Spurious errors with unique rules
See original GitHub issueI am getting spurious errors when running a few of the unique rules
Repro: https://github.com/zakodium/eslint-config-graphql (the failing-rules
branch) with npm run test
You can see the 5 unique rules that fail in this diff: here
The tested schema / document files are here, the error output can be seen here
It’s running graphql-eslint v0.8.0
I hope this helps and I’m not missing anything obvious
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:10
Top Results From Across the Web
Spurious relationship - Wikipedia
In statistics, a spurious relationship or spurious correlation is a mathematical relationship in which two or more events or variables are associated but ......
Read more >Spurious Correlation: Definition, Examples & Detecting
A spurious correlation occurs when two variables are correlated but they don't have a causal relationship.
Read more >Eliminating Spurious Error Messages Using Exceptions ...
This paper presents a discipline for tracking unavailable values and avoiding cascading error messages. The discipline extends the error monad ...
Read more >How Ignoring Measurement Error and Environmental ... - jstor
Spurious Certainty: How. Ignoring Measurement Error and. Environmental Heterogeneity. May Contribute to Environ - mental Controversies.
Read more >An Approach for Minimizing Spurious Errors in Testing ADA ...
We propose an approach for detecting deadlocks and race conditions in Ada tasking software. It is based on an extension to Petri net-based...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes tests pass now!
there are no false positives for
graphql-eslint/unique-type-names
anymore. Thanks!Other rules are still failing though, should I open a separate issue for each one of them?
https://github.com/zakodium/eslint-config-graphql/runs/2618345467
I don’t think you can see the action logs so here is an image: