refactors and enhances tip modal #1964
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#1964
Loading…
Reference in a new issue
No description provided.
Delete branch "tiplogic"
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?
Tip modal now disables send button on all invalid actions and shows feedback.
This looks good. There is one bug I see where if I type a small number I see scientific notation. We should avoid this.
Oh, I remember noticing that before. Modification on line 85.
Not strictly necessary, but splitting the "tip must be a valid number with no more than 8 decimals places" into more messages would improve UX:
I hear you. I'm glad to get specific input on the actual messages.
I'll have something shortly.
I'm noticing this functionality duplicated in 3 places: Publish>deposit, page>file>...>walletSendTip, and Wallet>walletSend. All three are basically the same FormField that informs a button to be disabled. The form field could stand to be wider as well, I think. Thoughts? Make it component?
I think making the input/label into it's own component sounds like a great idea!
@jessopb any updates here? Will the last comments also occur in this PR or a separate one?
The latest commit does precisely what @kauffj suggests.