-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ignore "extend schema" in .graphql files #1910
Comments
this issue will be fixed after adding federation support #1824 |
Ok thank you @B2o5T, is there a tentative plan when this will be available? |
Until end of year |
Meanwhile is there a work around? I tried |
The directives work fine with files without parsing errors (extend in this case). But, they don't work with files that have extend on top. Is there a work around to ignore this part from parsing, until this feature is implemented? |
Hi! Since this is reported as a parsing error, eslint directives are ignored. Is there any workaround? |
@MarcCoquand @gunes-sayin @gituserjava fixed in 4.3.0, your federation subgraphs should be parsed without parsing errors now #2812 (comment) |
We use below
extend
line in our .graphql file for federation and we get below error.Code snippet:
Error:
0:0 error Parsing error: [graphql-eslint] Error while loading schema: Directive "@link" may not be used on SCHEMA
Could you please advise on how this issue can be bypassed during graph ql eslint process?
The text was updated successfully, but these errors were encountered: