Implemented NestedWillPopScope for later handling PopScopes #221
Open
PcolBP wants to merge 4 commits intoBilalShahid13:masterfrom
Open
Implemented NestedWillPopScope for later handling PopScopes #221PcolBP wants to merge 4 commits intoBilalShahid13:masterfrom
PcolBP wants to merge 4 commits intoBilalShahid13:masterfrom
Conversation
Implement NestedWillPopScope Updated dependencies
Separate file to in nested widgets import only this one without other stuff
|
Can we get this PR merged, please? It seems like a really great solution to a relatively small but difficult problem |
Author
|
@ashishbeck as a temporary solution before this PR will be merged, you can fork my repository and then use it in your project like this in pubspec.yaml : |
|
Thanks |
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
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.
I've implemented NestedWillPopScope with null-safety.
Separated so if later need to be used no need to implement all data from package just this file.
Updated dependency as well.
All behaviour from before stays the same.
Potential fixes of:
This PR contains no breaking change.