Validate complains about fragments (false negative)
See original GitHub issueI am not really sure what to think about this. For example I have a simple file WareUnitFragment.graphql.ts
with this content.
import gql from 'graphql-tag'
export const WareUnitFragment = gql`
fragment GWareUnit on WareUnit {
id
enum
code
}
`
Running the validate for that file outputs…
error in src/segments/menu/graph/WareUnitFragment.graphql.ts:
- There can be only one fragment named GWareUnit.
- Fragment GWareUnit is never used.
- Fragment GAddress is never used.
- Fragment GCustomer is never used.
- Fragment GEmail is never used.
...
It lists all fragments used in the app. And this goes on for every file including fragments
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
The 'unknown knowns' in fragment screening - ScienceDirect
This Digest discusses some of these problems and offers suggestions to avoid them.
Read more >Sentence Fragments - Purdue OWL
Fragments are incomplete sentences. Usually, fragments are pieces of sentences that have become disconnected from the main clause. One of the easiest ways ......
Read more >Edit text validations in fragments android - Stack Overflow
but i am validating submitting the frag1 and frag2 details in fragment 2 only. if anything wrong 1 fragment2 ,i can show error...
Read more >Detection validation: going atomic on false negatives
While there is no way to truly eradicate false negatives from an environment, you can dramatically limit them through validation. By ensuring ...
Read more >Sentence Fragments | UMGC
A fragment is an incomplete sentence. It cannot stand alone because it is not an independent clause. It either lacks a subject, a...
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
@kamilkisiela Awesome, now it seems to be truly working. Even correctly detected deprecated field use. Thank you!
@FredyC I made a mistake I think, and also I agree good idea to add tests.
I looked briefly at including multiple documents yesterday but got errors aswell so I will give it a go tonight and fix this mistake aswell.