dimaMachina / graphql-eslint

ESLint parser, plugin and set rules for GraphQL (for schema and operations). Easily customizable with custom rules. Integrates with IDEs and modern GraphQL tools.
https://the-guild.dev/graphql/eslint
MIT License
789 stars 104 forks source link

require-import fragment does not support module paths #2180

Open jksmithing opened 6 months ago

jksmithing commented 6 months ago

Is your feature request related to a problem? Please describe.

In monorepos it's a common pattern to organize code across multiple internal packages.

Currently it's not possible to import a GQL fragment using a module path to an internal package, e.g. #import '@company/graphql/FooFields.gql'.

Describe the solution you'd like

I'd like to add support for module paths.

Describe alternatives you've considered

Relative paths: These work today but are not ergonomic or consistent with best practices for imports in JS/TS files. Further, we cannot utilize the mappings provided by the package.json exports field.

Additional context

N/A