Custom/scoped popping and PopScope #50
Open
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
This is to pop the dialog within it's context. Popping in the `CoolAlert.show(context)` pops using the parent context (or root context in the example app) with falls back to a black/blank screen.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Introduced
PopScopewrapping theAlertDialogpreventing undesired navigation while the dialog is open. For example, a dialog popup show "Your account needs attention" preventing further interaction with the app until an issue is resolved.Further, popping of the dialog in the above case is only possible provided the dialog context via a button action. Thus, the confirm & cancel buttons both provide the
BuildContextof the dialog itself allow the buttons to pop the dialog and not it's parent widget/route.