Alternate way to parse custom graphql #829
Merged
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.
because of swc bug swc-project/swc#3062, can't define custom graphql even if we're not parsing custom graphql with swc because it leads to other things breaking e.g. when using
@swc/jest
.this provides an alternative way to define custom graphql in json until I figure out a better way or until swc bugs are fixed.
not documented yet since hopefully temporary
use in one of the examples and test in different client