Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Duplication in generated types
See original GitHub issueWhen using multiple operations it seems like all operation types are generated for each of them (the only difference between the generated files is the declare module '*/DocumentName.graphql' part). I think each file should only contain the matching types.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:8
- Comments:21 (11 by maintainers)
Top Results From Across the Web
Duplication - National Human Genome Research Institute
Duplication is a type of mutation that involves the production of one or more copies of a gene or region of a chromosome....
Read more >Gene duplication - Wikipedia
Gene duplications can arise as products of several types of errors in DNA replication and repair machinery as well as through fortuitous capture...
Read more >Avoid Duplicate Functions in Generated Code - MathWorks
Duplicate functions in the generated code are the result of function specializations. The code generator specializes functions when it detects that they differ ......
Read more >Duplicate Code - Refactoring.Guru
Duplication usually occurs when multiple programmers are working on different parts of the same ... If duplicate code is found in two different...
Read more >duplicate Type 'ResolverKey(kind=SchemaType, id=Mutation ...
While working on mutations I see the following error. Cause: duplicate Type 'ResolverKey(kind=SchemaType, id=Mutation)' generated in ...
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 Free
Top 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
I published v0.18.0, fixing this issue. Thank you, guys. I’d love to hear what you think about the behavior. I wrote a migration guide for it. Please check it.
Before publishing v0.18.0, I’d like you guys to double-check the problem we’re solving. Do you think this is enough? Glad for reactions within 24h maximum.
I’ve published a prerelease. Please try it by
yarn add -D graphql-let@latestif you have time. Thank you for you help.