Add encryption flow to redux #59
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
Invalid
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/lbry-redux#59
Loading…
Reference in a new issue
No description provided.
Delete branch "redux-encryption-flow"
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?
See lbryio/lbry-redux#36
lbryio/lbry-desktop#1097 will be updated tomorrow with a dependency on these changes.
This should not be here, I will check my local commits and try to find why this change is appearing.
Guessing it's from Prettier.
A few minor comments.
What if this command fails?
@ -9,0 +10,4 @@
// TODO: Split into common success and failure types
// See details in https://github.com/lbryio/lbry/issues/1307
type ActionResult = {
type: any,
There should probably be an error attribute here too. Not sure what the daemon returns but it would be nice to know if there was an error decrypting or some unrelated error.
I would use
createSelector
here like you did below.We should add Flow types to this.
@ -9,0 +14,4 @@
result: any,
};
type WalletState = {
Maybe
EncryptActionResult
?I think we should rename that type to specify it's related to encryption
@ -9,0 +14,4 @@
result: any,
};
type WalletState = {
Likely it'll split into multiple at some point.
We don't have any predictable pattern at the moment and this only contains
result
and could apply to any other action, I can change it but I still think we'll end up with another common pattern.@ -9,0 +14,4 @@
result: any,
};
type WalletState = {
👍