feat: Enhance payout and status event filtering in the Human Protocol SDK#3314
Merged
feat: Enhance payout and status event filtering in the Human Protocol SDK#3314
Conversation
… SDK - Added chain_id parameter to PayoutFilter and StatusEventFilter classes for better network specificity. - Introduced pagination support (first, skip) and order direction in PayoutFilter. - Updated GraphQL queries to accommodate new filter parameters for payouts. - Implemented new StatusEventFilter class for filtering status events based on various criteria. - Enhanced EscrowUtils with methods to retrieve payouts, including validation for addresses and chain IDs. - Added comprehensive unit tests for the new payout functionality and updated existing tests for status events. - Refactored existing code to improve clarity and maintainability.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
portuu3
approved these changes
May 5, 2025
flopez7
added a commit
that referenced
this pull request
May 21, 2025
… SDK (#3314) * feat: Enhance payout and status event filtering in the Human Protocol SDK - Added chain_id parameter to PayoutFilter and StatusEventFilter classes for better network specificity. - Introduced pagination support (first, skip) and order direction in PayoutFilter. - Updated GraphQL queries to accommodate new filter parameters for payouts. - Implemented new StatusEventFilter class for filtering status events based on various criteria. - Enhanced EscrowUtils with methods to retrieve payouts, including validation for addresses and chain IDs. - Added comprehensive unit tests for the new payout functionality and updated existing tests for status events. - Refactored existing code to improve clarity and maintainability. * Update docs
This file contains hidden or 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
2 participants
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.
Issue tracking
#3310
Context behind the change
How has this been tested?
Executed some local tests and also ran unit tests
Release plan
Deploy new SDK version
Potential risks; What to monitor; Rollback plan
Check if
syncJobStusescron job is executed properly in Job Launcher