Refactoring suggestions about graphql-eslint HOT 5 OPEN

ESlint has a feature for this: https://eslint.org/docs/developer-guide/working-with-rules#providing-suggestions
Suggestions are not fixes, they will not be applied automatically, but will require the user to take an action to apply them. It was added specifically for the cases where there's no way to be sure that automatic change will make sense to the end user.

Finding duplicate code, however, is an np-complete problem, that's not trivial to implement even with a low guarantee.

from graphql-eslint.

This sounds very interesting. Any idea how can we locate those in a robust way what won't create incorrect results?
We can find similar selection sets (with TypeInfo) and suggest on moving to fragments, but that might not fit all use-cases...

from graphql-eslint.

Some of them already implemented in GraphQL Altair: altair-graphql/altair#745 (comment).

from graphql-eslint.

One other thing to keep in mind: ESLint operates on one file at a time, so if you have duplicate code across multiple files, ESLint will not be able to handle that, it will only be able to make a suggestion if it sees duplicate code in the same file.

from graphql-eslint.

no-one-place-fragments will be included in next release 3.14.0 to catch

find fragments that are used only in one place and suggest inline them.

from graphql-eslint.