store user supports #144
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
Invalid
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/lbry-redux#144
Loading…
Reference in a new issue
No description provided.
Delete branch "supports"
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?
The new sdk removed supports from
claim_list
, so we have to fetch and store them on our ownI just moved the old reducer functions to use the
handleActions
util. The actual changes I made are from here.L92 - L133
@akinwale not sure you can unlock tips in the android app, but if you can, you will need to use this.
Desktop commit to work with it:
6f1201d898
lgtm
@ -86,1 +88,4 @@
export const selectSupportsById = createSelector(
selectState,
state => state.supports || {}
);
If we set the default state values to
{}
, are the or clauses lines really necessary? (more curiosity than an objection)@ -86,1 +88,4 @@
export const selectSupportsById = createSelector(
selectState,
state => state.supports || {}
);
I've been doing that to safeguard if the value ends up being set to
null
orundefined
for some reason. Not that I noticed it happening, but just in case.