Actionable error message for duplicate priorities in update-flag

Open Beginner friendly
#8,301 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend

Research direction

Locate the update-flag handling for duplicate priorities and inspect the current error path. Change the message so it explains the conflict and tells users to provide explicit priority values, then confirm that duplicate priorities still produce an actionable error.

Written by the indexing model from the issue text.

Description

One small nit left IMO: I'd make the error message actionable so users understand why we can't accept ambiguous priorities. Something among the lines of The overrides for seg1 and seg2 are in conflict; provide explicit priority values.

Originally posted by @khvn26 in https://github.com/Flagsmith/flagsmith/pull/8102#discussion_r3787215841

Dominant language
Python
Stars
6.6k
Forks
571
Avg merge
1d 16h
Merged PRs (30d)
116

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Flagsmith/flagsmith

All issues in Flagsmith/flagsmith

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.