-
Notifications
You must be signed in to change notification settings - Fork 94
Ignoring a literal file with eslint-disable #102
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
It would also be useful to do this on a per-line basis. Would this be difficult?
|
In case it helps to unblock anyone, I just tested the following locally on This does not work:
This works:
Unfortunately this means that until one can migrate away from the deprecated field, any other fields within this query which are subsequently deprecated will not be caught by the linter. |
Running into the same issue with #import "./serverOnlyFragment.graphql"
#import "./sharedFragment.graphql"
# eslint-disable graphql/template-strings
# eslint-disable-next-line graphql/template-strings
query HomePageServer( # eslint-disable-line graphql/template-strings
# eslint-disable-next-line graphql/template-strings
$isAuthenticated: Boolean! # eslint-disable-line graphql/template-strings
$gpid: Long! # eslint-disable-line graphql/template-strings
$latitude: Float! # eslint-disable-line graphql/template-strings
$longitude: Float! # eslint-disable-line graphql/template-strings
$tld: String! # eslint-disable-line graphql/template-strings
) {
...ServerOnlyFragment
...SharedFragment
} Expected Would be stoked to get support for eslint-disable functionality, or of exhaustive checking of imports for rules |
Also having the same is as @cosmonot1 |
+1 for per-line disabling |
Hey guys, thanks for this plugin! Probably going to make our life a lot easier :)
I'm having a couple problematic queries that I cannot immediately change in order to be validated (mostly unions with field type conflicts behind the same alias - query executes, but the validator is not a big fan), and I noticed that
# eslint-disable
does not seem to have any effect right now. Would it be feasible to add support for this, or is there currently a workaround?The text was updated successfully, but these errors were encountered: