We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm not entirely sure because the naming linting does apply to query names, but not fragment names (on relay v14.0.0)
In the code for the graphql-naming rule I see this:
const CREATE_CONTAINER_FUNCTIONS = new Set([ 'createFragmentContainer', 'createPaginationContainer', 'createRefetchContainer' ]);
It seems like it's just checking these container functions which aren't in the latest relay which uses hooks like useFragment.
useFragment
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm not entirely sure because the naming linting does apply to query names, but not fragment names (on relay v14.0.0)
In the code for the graphql-naming rule I see this:
It seems like it's just checking these container functions which aren't in the latest relay which uses hooks like
useFragment
.The text was updated successfully, but these errors were encountered: