-
Notifications
You must be signed in to change notification settings - Fork 47
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
Would you consider adding lint for deprecated #136
Comments
We do have some rules around deprecations in
It might be useful for you to integrate it, as an additional linting layer. |
thanks @dotansimha ... couple reasons why i would hope relayjs-eslint would add this
|
feel free to create an issue, we would love to help ;)
Agree. But I think this might be out of scope for the Relay compiler? as this is a lint issue? 🤔
Actually, that might be interesting. If relay-compiler (rust) version has some built-in rules, we can use that and integrate it directly into the IDE using the ESLint extension. @B2o5T what do you think? |
@dotansimha what got me thinking it could [one-day] be possible, is these kinds of changes released in latest relay |
@dotansimha Yes, we can do it as we already do with graphql-js rules
@eMerzh there is nothing wrong with graphql-eslint, take a look at working examples |
Hello, i'm trying to add a linter for deprecrated fields on my project,
our schema is quite large, and i struggle to find a linter that could do it well...
i was wondering if you would consider adding one in the project?
i might try my hand at it
The text was updated successfully, but these errors were encountered: