Enabled #63
Open
Enabled #63
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📖 Description
Possibility to enable or disable the killswitch.
When we want to force an update, if the app goes into the background and then returns to the foreground, it reopens the alert, and gradually, the background becomes increasingly darker.
🤓 Solution
I added a parameter enabled that allows the validation to be activated or deactivated. For example, if I set enabled to true on the first render and later set it to false, when I put the app in the background and then return to the foreground, there are no more multiple alerts.
🦀 Dispatch
#dispatch/react#dispatch/react-native