Skip to content
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

Eslint config: disable 'relay/graphql-naming' rule #1459

Merged
merged 3 commits into from
Dec 4, 2020

Conversation

mrtnzlml
Copy link
Member

@mrtnzlml mrtnzlml commented Dec 4, 2020

This rule is no longer accurate, see: facebook/relay@ff1c10b

We might (partially) revert this commit after this PR gets resolved: relayjs/eslint-plugin-relay#107

This rule is no longer accurate, see: facebook/relay@ff1c10b

We might (partially) revert this commit after this PR gets resolved: relayjs/eslint-plugin-relay#107
@vercel vercel bot temporarily deployed to Preview – universe-example-relay December 4, 2020 15:56 Inactive
@vercel vercel bot temporarily deployed to Preview – universe-sx-tailwind-website December 4, 2020 15:56 Inactive
@vercel vercel bot temporarily deployed to Preview – universe-sx-tailwind-website December 4, 2020 15:59 Inactive
@vercel vercel bot temporarily deployed to Preview – universe-example-relay December 4, 2020 15:59 Inactive
@kodiakhq kodiakhq bot merged commit 10fdc0c into master Dec 4, 2020
@kodiakhq kodiakhq bot deleted the eslint-disable-relay/graphql-naming branch December 4, 2020 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

relay/graphql-naming: Relay no longer enforces fragment name with *_<propName>
2 participants