Skip to content

Add warning for conflicting command-line options #1222

@Steven6798

Description

@Steven6798

Introduce a new diagnostic to detect and warn when users pass conflicting command-line options (e.g. --warn-mismatch vs --no-warn-mismatch). This helps catch unintended or ambiguous behavior at invocation time.

Additionally, document best practices for handling conflicting options:

  • For users: clarify expected precedence rules and recommended usage
  • For developers: define consistent patterns for declaring, resolving, and validating mutually exclusive or overriding flags

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions