Comments (7)
matthieu-foucault
commented on May 14, 2024
6
I do have an issue where relay/unused-fields does not output information about the line number, making the warning easy to miss when only looking at the IDE
from eslint-plugin-relay.
nirvdrum
commented on May 14, 2024
5
The project at large works with TypeScript, but plugin:relay/recommended enables relay/generated-flow-types, which doesn't work in any non-Flow project. That needs to be explicitly disabled in the ESLint rules configuration. I was inquiring about a parallel rule set to relay/generated-flow-types that would provide a similar type of linting with TypeScript in mind.
from eslint-plugin-relay.
sibelius
commented on May 14, 2024
what does not work with typescript?
If you use @typescript-eslint/parser it should work
from eslint-plugin-relay.
natelindev
commented on May 14, 2024
I'll try with PR #115, no promises
from eslint-plugin-relay.
reckter
commented on May 14, 2024
I managed to get it working in #128, thanks to @llldar work in #115 :D
from eslint-plugin-relay.
gajus
commented on May 14, 2024
What dose generated-flow-types do?
from eslint-plugin-relay.
alloy
commented on May 14, 2024
#128 has been merged
from eslint-plugin-relay.
Related Issues (20)
- must-colocate-fragment-spreads gives false errors with yarn workspaces HOT 1
- must-colocate-fragment-spreads fails on sibling index.js imports
- readInlineData: missing argument check HOT 4
- relay/graphql-naming: Relay no longer enforces fragment name with *_<propName> HOT 1
- No line numbers for unused-fields? HOT 1
- Spreading props causes issues with unused-fields HOT 1
- Fixes should adhere to `artifactDirectory` configured in `relay.config.js`
- Relay 13: some explicit types are no longer required
- relay/must-colocate-fragment-spreads not working as expected on union types
- Would you consider adding lint for deprecated HOT 5
- graphql-naming rule doesn't seem to work on fragments in useFragment hook
- Rules are missing docs HOT 2
- What's the plan for the future of this plugin? HOT 3
- unused-fields rule don't respect typescript's typeof value
- RFC: add an `ignore` option to the `must-colocate-fragment-spreads` rule
- Pass/Fail Examples for Each Rule?
- unused-fields doesn't support fragments spread HOT 1
- Should using plugin:relay/{recommended,strict} should automatically reference the plugin?
- Issue upgrading to 1.8.0 HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from eslint-plugin-relay.