-
-
Notifications
You must be signed in to change notification settings - Fork 747
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
Subscription is not working with Variables #1157
Milestone
Comments
Thanks for filing this issue. I will look into it once I am back from Kiev. |
michaelstaib
added
🔍 investigate
Indicates that an issue or pull request needs more information.
bug
and removed
🔍 investigate
Indicates that an issue or pull request needs more information.
labels
Oct 26, 2019
I can proof now that this is a bug. We will issue a fix for this today. |
This one is fixed with 10.2.0-rc.1 |
This issue seems to be back in the 11 branch. I reopened this so we have a trigger to revalidate this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Subscriptions will not work when using variables, because when creating subscriptions stream keys, the variables names are used to create the keys, instead of the actual value of the variable.
This results is, that subscriptions that use variables will never receive any messages, because their stream key is never matched.
To Reproduce
Check out this repo (It's a fresh dotnet core 3 project with hc 0.10):
https://github.com/Narmor/hc-subscription-bug
Start the project, open Playground on http://localhost:5000/playground, create 4 editor-tabs and put the following snippets in one tab each:
first editor-tab
second editor-tab
with Variables:
third editor-tab
fourth editor-tab
with Variables:
Start both Subscriptions in the first two editor editor-tabs.
Then fire both mutations in the other two editor-tabs.
Expected behavior
Both open subscriptions will receive exactly the same two values.
The text was updated successfully, but these errors were encountered: