Thumbnail edit improvements #1586
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#1586
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "edit-thumbnail"
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?
https://github.com/lbryio/lbry-app/issues/1584
This looks good functionally according to my testing!
Aside from improving the name of
STATUSES
, I would not consider any of this feedback to be necessary to address to merge.@ -2,3 +2,3 @@
import * as React from 'react';
import { isNameValid, buildURI, regexInvalidURI } from 'lbry-redux';
import { isNameValid, buildURI, regexInvalidURI, STATUSES } from 'lbry-redux';
import { Form, FormField, FormRow, FormFieldPrice, Submit } from 'component/common/form';
what kind of statuses are these?
How feasible (and beneficial) would it be to split the entirety of this into a separate component?
This design forces the user to wait for the upload to finish before clicking Publish and it may not be clear why they're waiting.
It would be preferable if Publish could be clicked regardless of the upload status and instead the app waited for the remote upload to finish before making the
publish
API call.(Fixing this may be tricky, and if it's complicated probably shouldn't be considered blocking.)
Not hard. We could just move this into the
SelectThumbnail
component.@ -2,3 +2,3 @@
import * as React from 'react';
import { isNameValid, buildURI, regexInvalidURI } from 'lbry-redux';
import { isNameValid, buildURI, regexInvalidURI, STATUSES } from 'lbry-redux';
import { Form, FormField, FormRow, FormFieldPrice, Submit } from 'component/common/form';
spee.ch api status'. Agreed we should probably rename.
Until we move add this functionality somewhere else I think it's ok right now
👍