Channel edit4 #2584
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#2584
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "channelEdit4"
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?
Feature:
Channel page updates
Re: #561
Should be broken out of the channel page - probably requires useContext wrapper.
Not happy with upload function living in component.
Still a bug with updating and status messaging on submit.
Mostly unstyled.
This is close, we should pull out the channel edit functionality into it's own component, and re-use any publish form logic that we can.
Not needed
We already use the
uuid
module, lets just use that here.@ -23,19 +26,24 @@ type Props = {
location: { search: string },
history: { push: string => void },
For now lets just create a
channelEdit
component and put all of the edit stuff in there.<div className="card__actions">
We use this same logic in the publish form. Lets pull it into it's own function.
It can accept
bid, balance, amount
and return an error if it's bad. If there is no error, update the form, if there is an error, setErrorflow doesn't like import {v4 as uuidv4} from uuid;
DIdn't do this yet.
I'm thinking checkBidStuff(amount, balance, bid, errorFn, updateFn) would be the signature? Or do I misunderstand you?
This has been updated.