-
Notifications
You must be signed in to change notification settings - Fork 82
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
Controller-based mutations don't "trigger" subscriptions #74
Comments
I have forked this repo and made a very naive/messy attempt to prove the problem with a test. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I can expand on this as much as you want so I'll just put down the basic info for now.
If I have a mutation in a phoenix controller (in a
@graphql
module attribute), like this:And if this mutation is meant to trigger a subscription, for example if my
schema.ex
is like this:then the subscription is not triggered. This might have something to do with how the Absinthe.Phoenix SDL is processed differently to normal Graphql SDL.
The text was updated successfully, but these errors were encountered: