Open clehene opened 2 years ago
Note that some languages (including C++) hoist enum values into the parent namespace, which can result in conflicts for enums with the same values in the same proto package. To avoid this, multiple enums in the same proto package must not share any values. To avoid sharing values, APIs may prefix enum values with the name of the enum. In this case, they must do so consistently within the enum.
I make this rule by this note, maybe I need a setting page to config AIP spec.
It will relate to #45
@devkanro one thought - maybe it would make sense to externalize/delegate linting to a separate tool/config
Separate tool can't provide quick fix advice (fix one file/ fix one line). I think it's worth integrating lint functionality into language plugins for smarter quick fixes. This plugin is still lacking in custom lint rules, something like the api-lint.yml will be useful.
+1 this rule is annoying af.
"Value name of root enum should be start with enum name"
https://google.aip.dev/126