feat: implemented event triggers #103
Open
+3,053
−62
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
❗ Pull Request Information
This PR implements Hasura event triggers for escrow_transactions to monitor changes in status and refund_status. It ensures proper communication with external APIs when the transaction state transitions.
🌀 Summary of Changes
Added Hasura event trigger escrow_status_update for status changes
Added Hasura event trigger escrow_refund_status_update for refund_status changes
Configured webhooks in storage-service to handle these triggers
Implemented logic to filter events and prevent unnecessary API calls
Updated Hasura metadata to include filtering for meaningful status transitions
🛠 Testing
Evidence Before Solution
Video: Before Fix - Loom Video
Evidence After Solution
Video: After Fix - Loom Video
🐂 Related Issue
This pull request will close #97 upon merging.
Make sure to follow the Git Guidelines for Atomic Commits and read Contributing Guide
The Pull request needs to have the format mentioned below in the Git Guideline
Contributing Guide
Git Guidelines
🎉 Thank you for reviewing this PR! 🎉