Skip to content
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

fix: [lw-12169] handle treasury or reserves type of rewards #1683

Merged
merged 2 commits into from
Jan 31, 2025

Conversation

vetalcore
Copy link
Contributor

@vetalcore vetalcore commented Jan 30, 2025

Checklist


Proposed solution

It is expected for Reward object not to have pool id for payments from the treasury or the reserves.
As a result we do not need to fetch pool details for such rewards.

Testing

Describe here, how the new implementation can be tested.
Provide link or briefly describe User Acceptance Criteria/Tests that need to be met

Screenshots

Attach screenshots here if implementation involves some UI changes

@vetalcore vetalcore self-assigned this Jan 30, 2025
@vetalcore vetalcore requested a review from a team as a code owner January 30, 2025 13:22
@pczeglik-iohk
Copy link
Contributor

pczeglik-iohk commented Jan 30, 2025

Allure Report

allure-report-publisher generated test report!

processReports: ✅ test report for bd9cfcc4

passed failed skipped flaky total result
Total 33 0 4 0 37

Copy link
Member

@rhyslbw rhyslbw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine from a code perspective

@vetalcore vetalcore force-pushed the fix/lw-12169-handle-treasury-or-reserves-rewards branch from 376389e to bd9cfcc Compare January 31, 2025 11:05
@vetalcore vetalcore merged commit 0c8e8a6 into main Jan 31, 2025
32 of 33 checks passed
@vetalcore vetalcore deleted the fix/lw-12169-handle-treasury-or-reserves-rewards branch January 31, 2025 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants