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

Allow configuring multiple graphqlUrl endpoints #63

Open
AaronBuxbaum opened this issue Mar 13, 2023 · 2 comments · May be fixed by #98
Open

Allow configuring multiple graphqlUrl endpoints #63

AaronBuxbaum opened this issue Mar 13, 2023 · 2 comments · May be fixed by #98

Comments

@AaronBuxbaum
Copy link

My current system has two GraphQL endpoints which are hit by two different GraphQL clients. This obviously isn't an ideal system, but we are migrating between systems and the graphs have name collisions preventing unification strategies.

Can we enable providing an array of endpoints instead of just a string?

@valendres
Copy link
Owner

Hey @AaronBuxbaum I'm really busy this weekend, I probably won't have a chance to look at this until next weekend. This feature sounds like a great idea and I'm open to it being introduced. If you're able/willing to tackle this one before I have a chance to, please feel free to submit a PR. 🙂

@ypresto
Copy link

ypresto commented Jul 10, 2024

For workaround: pass RegExp to graphqlUrl.

createWorkerFixture([...], { graphqlUrl: /\/graphql/ as any })

While its type only accepts string, it actually handles RegExp.

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 a pull request may close this issue.

3 participants