Add channel subscriptions count below author. #6867
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#6867
Loading…
Reference in a new issue
No description provided.
Delete branch "6746-channel-sub-count"
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?
Fixes
Issue Number: https://github.com/lbryio/lbry-desktop/issues/6746
What is the current behavior?
N/A
What is the new behavior?
Display channel subscription below authors.
Other information
PR Type & Checklist
PR Type...
What kind of change does this PR introduce?
PR Checklist...
Please check all that apply to this PR using "x":
Thank for the PR! We'll want this to say Followers to match the channel page.
We'll get a review on it soon otherwise!
Sure @tzarebczan , updated!
DId some more testing on this and noticed the API for sub count is being called multiple times- both on refresh and when coming from another page (i.e. related content click). In the latter case, saw it called 3x. @Ruk33 probably not the end of the world, but maybe you can take a look.
Thank you @tzarebczan you were right. I managed to fix it and merge the conflicts.
Great, thanks again!