add logic for reward codes #7
No reviewers
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbryinc#7
Loading…
Reference in a new issue
No description provided.
Delete branch "reward-codes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
So we can implement https://github.com/lbryio/lbry-desktop/pull/1935
Looks good to merge.
Just a minor note which is more of a design choice, since there are just two additional parameters to pass to the claim reward endpoint, you could probably have the parameters as optional method arguments which makes it easier to know what to pass at first glance.
@akinwale I started doing that but decided it might be better to just pass all params in. It will be easier to implement new rewards if they require additional params.
I added the params to
doClaimRewardType
options, instead of adding an additional method param.