Add support for Clickable channel names on Explore page headings (#1820) #2023
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#2023
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "clickable-channel"
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?
Based on this issue:
https://github.com/lbryio/lbry-desktop/issues/1820
I am new to lbryio, but I assume that channel name can be written in two ways:
@CryptoCandor#9152f3b054f692076a6882d1b58a30e8781cc8e6
Crypto Candor | @CryptoCandor#9152f3b054f692076a6882d1b58a30e8781cc8e6
I assume that channel name would always start with
@
. So I cut the string by@
signed, check if it has link, and pass that to categorylink. This solution maintain backward compatibility.I do not know where should I put the new function, but I do not want to clutter the render method. So I separate out as
getCategoryLinkPartByCategory
in this component.Awesome! Thanks for the contribution 🙂
I think this should work. I'll give it a test in a bit.
I think we will also need a function for stripping the claim id off of the category title so that we aren't displaying the claim id for every line. This could be similar to how you generate the categoryLink
category={this.trimClaimIdFromCategory}
(or something similar)Hey @chrisza4, thanks for checking out LBRY and the contribution! If you haven't already, please make sure to check out our contributing guide.
Can we send you LBC in appreciation for your work?
@seanyesmunt That is correct. Let's make sure we always trim claim id from category before send props to
CategoryList
component.@tzarebczan Yes you can. Do you need any information from me? My email is chakrit.lj@gmail.com
@chrisza4 please check out the FAQ that I linked, we'll need you to reach out to us. Also, please include a time estimate.
Thanks @tzarebczan . I will reach out to you once PR get merged.
Tested and it's working good!
@chrisza4 Can you add a changelog update? Then it's ready to merge.
Changelog updated
woohoo @chrisza4 , nice job getting through your first PR! Don't forget to reach out once it's merged :)
Awesome! I’ll merge this once I’m back at my computer
@chrisza4 Merged!