Add strict-non-nullable-variables rule #421
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vejrj
approved these changes
Jun 14, 2024
user1736
force-pushed
the
update-eslint-plugin-version
branch
2 times, most recently
from
ba75deb
to
98a8b48
Compare
user1736
force-pushed
the
update-eslint-plugin-version
branch
from
98a8b48
to
a8d6dd3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a rule that enforces following RFC.
In order to use proper methods for schema access within the new rule and to better align it with TMP codebase @graphql-eslint/eslint-plugin version was updated and all other rules were adjusted accordingly (no functional changes in them)