-
Notifications
You must be signed in to change notification settings - Fork 46
Issues: relayjs/eslint-plugin-relay
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
# eslint-disable-next-line
clashes with graphql-eslint
's processor
#153
opened Sep 24, 2024 by
alecmev
RFC: add an
ignore
option to the must-colocate-fragment-spreads
rule
#149
opened Feb 13, 2024 by
rbalicki2
unused-fields rule don't respect typescript's typeof value
#148
opened Dec 27, 2023 by
roman-antl-satoshilabs
graphql-naming rule doesn't seem to work on fragments in useFragment hook
#137
opened Mar 3, 2023 by
jmancherje
relay/must-colocate-fragment-spreads not working as expected on union types
#135
opened Jan 22, 2023 by
richardtagger
Fixes should adhere to
artifactDirectory
configured in relay.config.js
#130
opened Dec 15, 2021 by
reckter
relay/graphql-naming: Relay no longer enforces fragment name with *_<propName>
help wanted
#107
opened Dec 4, 2020 by
mrtnzlml
must-colocate-fragment-spreads fails on sibling index.js imports
#105
opened Oct 27, 2020 by
JonathanUsername
must-colocate-fragment-spreads gives false errors with yarn workspaces
#103
opened Aug 10, 2020 by
tbergquist-godaddy
Should using plugin:relay/{recommended,strict} should automatically reference the plugin?
#90
opened Apr 22, 2020 by
nirvdrum
erroneously flags fragments used as macros with @relay(mask: false)
#47
opened Jan 9, 2019 by
dnozay
field with __clientField directive should not be marked as unused imho
#35
opened Jul 15, 2018 by
steida
ProTip!
What’s not been updated in a month: updated:<2024-10-09.