Changes needed for additional youtube transfer UI #62
No reviewers
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
LBRYCommunity/lbryinc!62
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "onboarding"
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?
@ -3,2 +3,4 @@export const GENERATE_AUTH_TOKEN_STARTED = 'GENERATE_AUTH_TOKEN_STARTED';export const GENERATE_AUTH_TOKEN_SUCCESS = 'GENERATE_AUTH_TOKEN_SUCCESS';export const AUTHENTICATION_STARTED = 'AUTHENTICATION_STARTED';export const AUTHENTICATION_SUCCESS = 'AUTHENTICATION_SUCCESS';We were importing all of these from
lbry-redux. Not sure whyOne issue with the
doSetSyncmethod. Everything else looks good.While I understand the reasoning behind this,I feel it's a bit weird because it may be possible for the sdk to not have the updated balance after a second. Maybe we could also explore using messages like "your wallet balance will be updated shortly" or something similar. Not really a blocker though.
Should we rename this to something more descriptive? Right now, this calls
/sync/set, and then sets the default account if the hashes are different, and finally unlocks the the wallet if it's locked. It is also possible for theaccount_unlockcall to fail with an error. If that happens, shouldSET_SYNC_FAILEDbe dispatched?Alternatively, we could have two methods. One for calling
/sync/setand the another one calling/sync/setwith the extra steps.Yeah, I agree it's not a very good solution. I think the better fix is to wait for the SDK to add balance updates through sockets.
I think it makes it a lot nicer to work with if theres just one method. But I can add a parameter to the function that triggers the additional steps
After looking at this again after your comment I realized it should have been pulled out. I put it in
doGetSyncwith a flag that starts the additional steps. This shouldn't require any changes from you.Looks good.