@graphql-eslint/naming-convention: query should or should not start with a verb

For example if

eslint @graphql-eslint/naming-convention: [“error”, {“QueryDefinition”: [“camelCase”, “shouldStartWithVerb”]}]

correct:

type Query {
    getUser(id: String): User
}

incorrect:

type Query {
    user(id: String): User
}

type Query {
    GetUser(id: String): User
}

Let me know if you would be open to this contribution (if this does not exist yet) and if yes what the correct rule configuration format should look like.

I was thinking of letting QueryDefinition take an array of values that can include shouldStartWithVerb and shouldNotStartWithVerb

[DianaSuvorova]

@B2o5T Beautiful! Just tried it – works exactly as I need. Apologies for the confusion here. Thank you so much!

[B2o5T]

What I think is a bad practice in GraphQL to name queries with get prefix But, @DianaSuvorova with graphql-eslint you still can force to name your queries with no matter what prefix.

For query like

type Query {
  user(id: ID!): User
}

and with options

# eslint @graphql-eslint/naming-convention: ['error', { QueryDefinition: { style: 'camelCase', prefix: 'get' } }]

It’s will report an error Query name "user" should have "get" prefix according to your needs