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

feat: Allowing # import in GraphQL #141

Merged
merged 32 commits into from
Aug 8, 2020
Merged

feat: Allowing # import in GraphQL #141

merged 32 commits into from
Aug 8, 2020

Conversation

piglovesyou
Copy link
Owner

Fixes #65
Fixes #95

@piglovesyou piglovesyou merged commit 3f2a3d5 into master Aug 8, 2020
@piglovesyou piglovesyou deleted the import-fragments branch August 8, 2020 10:08
@jgoux
Copy link

jgoux commented Aug 8, 2020

Congrats for this feature Soichi! 🎆

I was wondering what is the story for using fragments with the babel plugin?

Also, does graphql-let export typescript types? I reuse them a lot when defining a fragment, for example : https://gist.github.com/jgoux/153804f6b9922127234ae9f595a754e4

I tried to contact you on Twitter but your DM are closed. 😄

@piglovesyou piglovesyou changed the title feat: Alloing # import in GraphQL feat: Allowing # import in GraphQL Aug 8, 2020
@piglovesyou
Copy link
Owner Author

Hi @jgoux, thank you for reaching me! So currently CLI and babel can handle this, with .d.ts generation.

I'm afraid I couldn't get 100% from your example, but yes, this change enables reusing GraphQL document fragments like this used by this. I hope this description works for you. Soon I'll announce v0.15.0 on Twitter so maybe some discussion will start there.

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.

Migrating to Apollo Client 3.0 issue Example with fragments
2 participants