Subscriptions not working with different path
See original GitHub issueThis issue pertains to the following package(s):
- GraphQL Playground Express Middleware
What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?
1.4.3
What is the expected behavior?
If I specify a different subscriptionsendpoint, it should work.
What is the actual behavior?
It doesn’t. It tries to connect to /graphql
(my ‘normal’ endpoint)
What steps may we take to reproduce the behavior?
Please provide a gif or image of the issue for a quicker response/fix.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:9
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Subscriptions not working with different path #462 - GitHub
Subscriptions not working with different path #462. Open. 1 task done ... If I specify a different subscriptionsendpoint, it should work.
Read more >New subscription not added to any directory - Microsoft Q&A
Every subscription has to be associated with a azure Active directory when its created. You can not have a subscription without a directory...
Read more >Unable to move a domain to the existing subscription
Unable to move a domain to the existing subscription: the target path already exists.
Read more >Not all Azure subscriptions accessible in Visual Studio 2015
I found a way around this inside the Azure Portal. You can move subscriptions between different directories. Ovbiously the Visual Studio has problems...
Read more >Troubleshoot Subscriptions - Tableau Help
Resume suspended subscriptions ... Administrators and subscription owners can resume subscriptions in several ways: ... When a subscription is resumed, the alert ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It’s not reading the
.graphqlconfig.yml
. For me, queries and mutations are working fine. But subscriptions are not working. That’s the only reason I don’t use Playground. I was trying the express middleware.Note changing subscriptionEndpoint to the option that is being expected doesn’t fix the problem (like below)
https://github.com/prisma/graphql-playground/blob/fc871b6b021a07664f2fd57d91f72693d8af8d3a/packages/graphql-playground-html/src/render-playground-page.ts#L95
shouldn’t it be
(options as any).subscriptionEndpoint
(/s/tionsEnd/tionEnd)