-
-
Notifications
You must be signed in to change notification settings - Fork 257
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
[Hasura] Include Option to Specify Trigger Name in Hasura Event Handling Decoration #152
Labels
enhancement
New feature or request
Comments
Hey @n3n Thanks for opening this issue, I think this is great feedback and it definitely makes sense that targeting the trigger name would give the user a lot more flexibility for properly subscribing to events. I'll do my best to spend some time improving this feature this week |
WonderPanda
added a commit
that referenced
this issue
May 24, 2020
deprecates the old model of binding events based on the source schema and table to one that leverages the hasura trigger name fixes #152
Good!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hasura events can have more than one trigger for a schema/table/op. It would be better if the decorator accepts the
trigger.name
as an option, so we don't need to care about schema/table/op.We can also create an event trigger to listen different column with the same schema/table/op
Example
Reference: https://hasura.io/docs/1.0/graphql/manual/event-triggers/payload.html#json-payload
The text was updated successfully, but these errors were encountered: