Skip to content

Actionable error message for duplicate priorities in update-flag #8301

Description

@khvn26

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 #8102 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions