📎 All caps ENUM in GraphQL

[eMerzh]

Description

it's well a convention (not a requirement) in GQL to have ALL CAPS enums,

a few eslint based linter have it like

https://github.com/joshuaNathaniel/eslint-plugin-graphql-schema/blob/master/docs/rules/enum-values-all-caps.md
or
https://github.com/cjoudrey/graphql-schema-linter

it might be a good new lint for biome :)

[eMerzh]

as a noob, i'd like to try my hand at that :)

i did created #4031

[minht11]

After doing quick search for enum graphql there are a lot of different casing examples, so this rule is likely too restrictive.
I think this functionality would be better served by useNamingConvention for graphql.
#4031 (comment)

[Conaclos]

I think this functionality would be better served by useNamingConvention for graphql.

It is a good point.
However, I think that our current infra and way of configuring rules doesn't allow a rule on several languages with a config shape different for every language.
@ematipico any input regarding this aspect?

[ematipico]

Configuring multiple rules shouldn't be difficult.

Here's what I thought:

• have an analyze crate where we move shared options and logic
• adjust the code to take the new crate into account
• consume those options from multiple rules
• be good at documenting the options. If there's overlap among languages, that's fine, but if an option is added for one language, the doc comments should say so