Flatten Navigation hiearchy #4233
Merged
Conversation
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
To make implementation of TwoPaneNav, this commit flattens the navigation hierarchy.
Also add a dummy preference for TwoPane preparation
nulldrf
pushed a commit
to nulldrf/lawnchair
that referenced
this pull request
Apr 10, 2024
* Simplify code of Preferences.kt * Flatten navigation hierarchy To make implementation of TwoPaneNav, this commit flattens the navigation hierarchy. * Reorganize a bit * Use nested NavGraphs for sub-destinations Also add a dummy preference for TwoPane preparation * Change highlight logic to use .contains() * spotlessApply
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.
Description
This PR flattens the Navigation hiearchy to simplify the implemenetation of the responsive Preference layout.
Type of change
✅: General change (non-breaking change that doesn't fit the below categories like copyediting)
❌ Bug fix (non-breaking change which fixes an issue)
❌ New feature (non-breaking change which adds functionality)
❌ Breaking change (fix or feature that would cause existing functionality to not work as expected)