Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alternate way to parse custom graphql #829

Merged
merged 3 commits into from
Apr 11, 2022

Conversation

lolopinto
Copy link
Owner

@lolopinto lolopinto commented Apr 5, 2022

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

because of swc bugs, we can't use decorators if swc/jest is being used in a project even if we're not (currently) using swc for custom graphql since tests start failing

workaround is to create a simplified json api that doesn't quite support the full API but supports just enough to gather the core data

hopefully, this is temporary and swc issues are fixed soon
@lolopinto lolopinto merged commit 3adbe36 into main Apr 11, 2022
@lolopinto lolopinto deleted the alternate-way-to-parse-custom-graphql branch April 11, 2022 20:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant