This repository has been archived by the owner on Oct 15, 2024. It is now read-only.
Remove fragments from the pool query, issue with generated types #122
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The generated pool type has the issue described here because of the nested fragments:
dotansimha/graphql-code-generator-community#140 (comment)
For the sake of simplicity, I just removed all of the nested fragments from the query, and the types are then generated as you'd expect.
Type of change
expected)
How should this be tested?
Please provide instructions so we can test. Please also list any relevant details for your test
configuration.
Visual context
Please provide any relevant visual context for UI changes or additions. This could be static
screenshots or a loom screencast.
Checklist: