Support channel definitions from /file/list_homepage #1267
No reviewers
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#1267
Loading…
Reference in a new issue
No description provided.
Delete branch "explore-channels"
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?
This PR for issue #1049
Is ready to be reviewed by @liamcardenas
Uses existing reducers, actions, selectors
Moves
component/common/category-list.jsx
to its own top level component atcomponent/categoryList
because it needs props tofetchChannel
and selectclaimsByChannel
andclaimsById
Fetches channels in
componentDidMount
when the category is a channelReturns false in
isCardVisible
when!section
-- this fixed the error I was getting; I'm not sure exactly how the code for the UI worksAdds const
channel
to theCategoryList
render
function, which is an empty array until the data comes in, and once the data comes in is an array of proper uris made with 'buildURIfrom
category` selector dataMaps the
channel
array to<FileCard>
components when appropriateDisplays a '
for a channel (
categoryLink,
names=[]) when
featuredUris[category].lengthis false in
DiscoverPage`Imports
CategoryList
from new location in Discover and Subscriptions pagesFixes various linting errors I found along the way
Includes fake data for demo/testing purposes to be removed after review/updates
This is really close. I think some of the logic can be removed since we already have code that handles this. It just uses the same data that page 1 of the channel page uses.
You can use the
Caim
type that I recently created.@ -0,0 +31,4 @@
super();
this.state = {
canScrollPrevious: false,
Use
makeSelectFetchingChannelClaims
to make sure we aren't already fetching for this channel.@ -0,0 +158,4 @@
}
}
}
👍
@ -0,0 +196,4 @@
scrollTarget = cards[0].offsetLeft;
}
scrollTarget -= firstCardOffsetLeft; // to play nice with the margins
A better name for this is probably
channelURIs
you should also be able to use
makeSelectClaimsInChannelForCurrentPage
, which is what the channel page uses. Just get the first page of content and you won't have to worry about this logic.This prop should just have a default value of
[]
These changes aren't needed anymore since subscriptions page isn't using this component
@ -0,0 +196,4 @@
scrollTarget = cards[0].offsetLeft;
}
scrollTarget -= firstCardOffsetLeft; // to play nice with the margins
I have tried using in the makeSelectClaimsInChannelForCurrentPage selector in place of the other two and the logic that goes with them, and I keep running into problems. I'm passing
props.categoryLink
as theuri
, which I think should be fine based on console logging props. I have tried various forms of the makeSelect pattern I found in the RewardLink container-component to no avail, including rewriting the selectors, but there are so many not-working version I'm not sure what to push/show you.@ -0,0 +196,4 @@
scrollTarget = cards[0].offsetLeft;
}
scrollTarget -= firstCardOffsetLeft; // to play nice with the margins
@skhameneh
This PR still contains sample data to demonstrate the functionality. I will remove it and clean up commit history following approval.
Lets merge this. @daovist once you remove the mock data I'll merge