Bind to bottomNavContainerFrame only if bottomNavItems not empty #2589
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
…r-setShowNavigationInDefaultLongScroll
LZRS
force-pushed
the
2588-fix-crash-for-setShowNavigationInDefaultLongScroll
branch
from
89245d2
to
d7e0a17
Compare
jingtang10
deleted the
2588-fix-crash-for-setShowNavigationInDefaultLongScroll
branch
santosh-pingle
pushed a commit
to santosh-pingle/android-fhir
that referenced
this pull request
Jul 8, 2024
…gle#2589) * Bind to bottomNavContainerFrame only if bottomNavItems not empty * Add tests for setShowNavigationInDefaultLongScroll
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.
IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #2588
Description
Checks bottomNavItems is not empty before binding to bottomNavContainerFrame
Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
Type
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Builds | Releases | Other)
Screenshots (if applicable)
Checklist
./gradlew spotlessApplyand./gradlew spotlessCheckto check my code follows the style guide of this project../gradlew checkand./gradlew connectedCheckto test my changes locally.