-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(bg/storage): use separate key to toggle continuous payments #727
Conversation
Extension builds preview
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now thinking about it, we might not even need to delete the enabled
key now, if we plan to introduce the global enabled
flag. We can just keep it for when that lands.
Yes, but its value isn't same as current meaning of enabled. We'll add it back (as new migration) with its new meaning. |
Update: oh yeah we can keep it. Just not use its value or set it yet. |
LGTM |
enabled
to continuousPaymentsEnabled
Context
Will help with #623 as decided in #654 (comment)
Then in future
enabled
will mean entire extension enabled or not, not just continuous payments.Changes proposed in this pull request
Storage.enabled
toStorage.continuousPaymentsEnabled
continuousPaymentsEnabled
to previous value ofenabled
enabled
totrue
for #623Notes to reviewer