User history #64
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#64
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "user-history"
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?
See lbryio/lbry-desktop/issue/1009
UserHistoryPage
toMy LBRY
in sidebarOne comment
@ -86,2 +85,4 @@
export const FETCH_BLACK_LISTED_CONTENT_FAILED = 'FETCH_BLACK_LISTED_CONTENT_FAILED';
export const BLACK_LISTED_CONTENT_SUBSCRIBE = 'BLACK_LISTED_CONTENT_SUBSCRIBE';
export const SET_PLAYING_URI = 'SET_PLAYING_URI';
export const SET_CONTENT_POSITION = 'SET_CONTENT_POSITION';
Do we need
SET_PLAYING_URI
if we haveMEDIA_PLAY
? Can that be used to set the same values?@ -86,2 +85,4 @@
export const FETCH_BLACK_LISTED_CONTENT_FAILED = 'FETCH_BLACK_LISTED_CONTENT_FAILED';
export const BLACK_LISTED_CONTENT_SUBSCRIBE = 'BLACK_LISTED_CONTENT_SUBSCRIBE';
export const SET_PLAYING_URI = 'SET_PLAYING_URI';
export const SET_CONTENT_POSITION = 'SET_CONTENT_POSITION';
I forgot to remove
MEDIA_PLAY
from this repo. I'll do so now and push...Aren't these pages app-specific and thus inappropriate for lbry-redux?
Even if is redux appropriate, this is a dangerous/fragile pattern - how would someone changing the name of a page or route know to update this function?
Yeah... This selector should probably live in the app.
Agreed.
Address the pending comments about moving pieces into the app, that aside looks good
Moved
selectNavLinks
into the app