New repost flow #5167
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#5167
Loading…
Reference in a new issue
No description provided.
Delete branch "repostFromSearchRebase"
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?
rebased version
Unused strings need to be cleaned up
Lets make these into their own components.
claimPreview/internal/{mature-contnet, ...}
comment
I think this should be
Support
instead ofStake
Move this somewhere inside the card or remove
You shouldn't need this comment
extra comment
I'm not sure what this comment means
@ -51,33 +60,68 @@ export default function SearchTopClaim(props: Props) {
}
Please use
className="empty empty--centered"
if we aren't usingclassnames
or a js variable in the classnameWrap this with
<div className={classnames({"card--disabled": balance === 0 })}
You don't need to check for
resolveUri
since it will always existI think this can just be
from
andto
so the URL is more readableNot needed now but something I've been thinking about for a while is changing
isSearching
to returntrue
if the lighthouse call hasn't returned yet or if the results from lighthouse aren't done resolving.just FYI, should help with some UI flashing issues
I don't think you need this lint comment
@ -24,2 +27,4 @@
name={channelActive ? `@${queryName}` : queryName}
defaultFreshness={FRESH_ALL}
defaultOrderBy={ORDER_BY_TOP}
meta={
Looking at the
queryName
line above... I think you can just doname={name}
?@ -26,0 +31,4 @@
<I18nMessage
tokens={{
repost: (
<Button
This doesn't need to be a new style. You can keep the
header
prop as it was, and pass the action text in with themeta
prop.https://github.com/lbryio/lbry-desktop/blob/master/ui/page/channelsFollowing/view.jsx#L35
meta={<I18nMessage>...
@ -97,11 +104,13 @@ export const makeSelectWinningUriForQuery = (query: string) => {
This should only return
pendingClaimUrl
if it's effective amount is greater thanclaim1
andclaim2
This shouldn't be needed if you bring the help text into the card on the repost page (or remove it)
@ -135,2 +152,3 @@
width: 5rem;
min-height: 5rem;
width: 8rem;
}
Generally, I have been trying to follow this pattern
@ -97,3 +97,15 @@
}
}
}
.claim-search__menu-group--between {
This shouldn't be needed if you use the
meta
propIt was "Deposit"..
@ -24,2 +27,4 @@
name={channelActive ? `@${queryName}` : queryName}
defaultFreshness={FRESH_ALL}
defaultOrderBy={ORDER_BY_TOP}
meta={
Tried it, can't do it - it doesn't switch what claimListDiscover searches that way.
@ -97,11 +104,13 @@ export const makeSelectWinningUriForQuery = (query: string) => {
refactored to return the claim. was simpler than I thought.