Skip to content

Consider making the checkSuspiciousEnumValue report a warning instead of an error #5

@markvl-sbp

Description

@markvl-sbp

Whenever there is a number in an enum value, the linter reports an error (Enum '%s' has suspicious value '%s' (line %d)). This may be suspicious, but is it really an error?

Could you consider making this a warning instead?

Example:

"Enumeration of Citroen car models."
enum Citroen {
  C3
  C4
  C5X
}

Result:

ERRO[0000] ERROR: Enum 'Citroen' has suspicious value 'C3' (line 13)
ERRO[0000]   Did you mean 'ID'?
ERRO[0000] ERROR: Enum 'Citroen' has suspicious value 'C4' (line 14)
ERRO[0000]   Did you mean 'ID'?
ERRO[0000] ERROR: Enum 'Citroen' has suspicious value 'C5X' (line 15)
ERRO[0000]   Did you mean 'ID'?

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