-
-
Notifications
You must be signed in to change notification settings - Fork 541
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: support GraphQL subscriptions #2357
base: main
Are you sure you want to change the base?
Conversation
761b4ce
to
eca6e43
Compare
eca6e43
to
1ddc187
Compare
403e143
to
e24e6db
Compare
@sutt0n, I do quite share your enthusiasm! |
is there an update or roadmap here to getting this into a new release, or suggestions on how to mock gql subscriptions in the interm? |
@thearchitector there's a Roadmap section in the description of this PR. It will get populated as I find more things that have to be done before this is ready. So far, it's that one point. You can follow the PR to see the gist of what GraphQL subscriptions support entails, and how you can use the existing
|
Important
If your team can benefit from the GraphQL subscriptions support in MSW, please consider sponsoring the project. This will be a big effort, and your contribution will help to see it through. Thank you.
Roadmap
ws.link
supportlogs: false
/quiet: true
to disable the default WebSocket handler logging for GraphQL subscriptions (it's an implementation detail).