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.

Sign up for GitHub

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

Jump to bottom

emphasize that schema transform are workarounds #4857

Open
Tracked by #5201
, #5667 ,  #6209
...
n1ru4l opened this issue Nov 17, 2022 · 3 comments
Open
Tracked by #5201
, #5667 ,  #6209
...

emphasize that schema transform are workarounds #4857

n1ru4l opened this issue Nov 17, 2022 · 3 comments
Assignees
@ardatan

Comments

@n1ru4l
Copy link
Collaborator

n1ru4l commented Nov 17, 2022

No description provided.

@mattfysh
Copy link

Hi @n1ru4l could you elaborate on why these are considered workarounds?

@n1ru4l
Copy link
Collaborator Author

n1ru4l commented Nov 26, 2022

@ardatanshould know

@mattfysh
Copy link

@ardatan can you shed some light here? I thought one of the features of graphql-tools is to wrap external schemas that we don't control, therefore I don't see any other way to stitch these schemas without using transforms

@theguild-bot theguild-bot mentioned this issue Apr 23, 2023
Open
@theguild-bot theguild-bot mentioned this issue Oct 26, 2023
Open
@theguild-bot theguild-bot mentioned this issue May 23, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ardatan ardatan

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mattfysh @n1ru4l @ardatan