Moar discovery #2553
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#2553
Loading…
Reference in a new issue
No description provided.
Delete branch "discovery-2"
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?
Building off my last PR
Changes
Most of this feedback is minor. Did not do a thorough UI/UX test, just code.
header
andnoHeader
could be a single param, unless it's considered a bad practice to say a type can be aNode
orboolean
(true = default, false = none, node = inject)Same for this, if this is being used on channels and files, call it
ClaimTags
channels aren't files
if this component is now rendering streams and channels, I'd rename it
ClaimListItem
or similarslightly worse pattern, because passing true for both large and slim should not be possible and would have unexpected behavior
good pattern!
I happened to have my app in Polish while running this branch and noticed this menu looks a little weird when the text of the items is longer than they are in English.
I also kind of dislike this from a UX perspective. I'd rather just put light/dark in settings, give Help first-class status, and lose the dropdown entirely if these are the only 3 items in it.
While I know we've used this approach elsewhere, it's a bad practice and doesn't really work for i18n.
Is there any ability to inject nodes inside of an i18n string? e.g.
__('You have %amount% LBC', { amount: <span>5</span> })
If not, let's use a comment tag so we can track where these exist. Something like
@i18nfixme
.@ -0,0 +16,4 @@
return (
<section className="card card--section card--reward-total" style={{ backgroundImage: `url(${TotalBackground})` }}>
<span className="card__title">
{integer} LBC {__('Earned From Rewards')}
https://github.com/lbryio/lbry/issues/2245
@ -0,0 +11,4 @@
resendVerificationEmail: string => void,
checkEmailVerified: () => void,
user: {
has_verified_email: boolean,
Should user be a first class type and/or should this value simply be selected directly off of the user?
looks like a nice refactor!
I'm pretty sure I can explain/fix this, but easier to do so synchronously. Please bring up on next standup we're both on.
empty class
@ -33,0 +55,4 @@
const options = {
channel_ids: ids,
};
is the channel uri guaranteed to have a
#
? they will never be URIs without a claim id?@ -17,0 +28,4 @@
.file-list__header--small {
height: 3rem;
font-size: 1em;
minor tsk tsk for BEM violation
@ -8,2 +6,4 @@
& > *:not(:last-child) {
margin-right: var(--spacing-small);
}
minor boos
@ -0,0 +1,31 @@
import { useEffect, useState } from 'react';
I approve of copy and pasting this wherever you copy and pasted it from
@ -33,0 +55,4 @@
const options = {
channel_ids: ids,
};
The channel id is required (for now?) in internal-apis for subscriptions. The app always uses the full uri for the subscribeButton component
@ -0,0 +1,31 @@
import { useEffect, useState } from 'react';
📈
@ -0,0 +11,4 @@
resendVerificationEmail: string => void,
checkEmailVerified: () => void,
user: {
has_verified_email: boolean,
Yes to both of these
Nice good call. Will rename all of these to
claimX
No I think that makes more sense. Will update.
Changed to
type={"small", "large"}
I'm fine with moving help out of the menu, but I would really like to keep the dark mode toggle. YouTube, Twitter, and Reddit all have a dark mode toggle in their drop-down menu.
Not with
y18n
. I would imagine this exists somewhere though