-
Notifications
You must be signed in to change notification settings - Fork 61
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
Reuse PermanentNavModel if provided in the list of navModels #605
Closed
KovalevAndrey
wants to merge
6
commits into
bumble-tech:1.x
from
KovalevAndrey:1.x-reuse-permanent-nav-model
+216
−30
Closed
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
d6f40a5
Reuse PermanentNavModel if provided in the list of navModels
KovalevAndrey 951653b
Update CHANGELOG.md
KovalevAndrey a6bd3de
Remove redundant comment
KovalevAndrey 4db8192
Add CombinedNavModel test
KovalevAndrey 3b9acf8
Use createPermanentNavModel method
KovalevAndrey 0230d63
Check that we're not nesting CombinedNavModel
KovalevAndrey File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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 file contains 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 file contains 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 file contains 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 file contains 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 file contains 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
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.
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.
It seems like it's possible (though maybe not advised?) that a developer could nest a
CombinedNavModel
within aCombinedNavModel
.Perhaps this case should be covered as well? (if so, then the init block for the CombinedNavModel might need to be updated).
If we don't want to allow nesting
CombinedNavModel
withinCombinedNavModel
perhaps theinit
block ofCombinedNavModel
could prevent this as well? (though this hypothetically could be a breaking change.i.e.
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.
yeah, I think we can prevent nesting of
CombinedNavModel
as it doesn't make much sense and harder to supportThere 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.
Nesting makes sense at the current moment.
First you pass
CombinedNavModel
viaParentNode(navModel = backStack1 + backStack2)
then thisCombinedNavModel
is merged with internalPermanentNavModel
into anotherCombinedNavModel
. So at the end we haveCombinedNavModel
insideCombinedNavModel
is a pretty basic case.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.
@KovalevAndrey it sounds like this might be wise to keep? otherwise you should definitely update the changelog to call this out as a breaking change.
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.
@LachlanMcKee Looking at the code I'm leaning towards removing the
PermanentNavModel
from parentNode at all and use it the same way as any other navModelsThere 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.
If we're using the provided API it doesn't get nested