Fix bugs related to validation snackbar display#7030
Merged
seadowg merged 3 commits intogetodk:masterfrom Jan 20, 2026
Merged
Conversation
seadowg
approved these changes
Jan 20, 2026
|
Tested with success Verified on device with Android 16 Verified cases:
|
|
Tested with success Verified on device with Android 12 |
|
Tested with success Verified on device with Android 10 |
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
5 participants
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.
Closes #7025
Closes #7026
Closes #7027
Why is this the best possible solution? Were any other approaches considered?
Nothing important to highlight here; I’m just adding some tweaks to handle invalid polygons (specifically, to display errors).
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
It should simply fix the issue, but please be careful as always and test other cases where the answer should be validated to avoid regressions.
Do we need any specific form for testing your changes? If so, please attach one.
Forms are linked in the issues.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
No.
Before submitting this PR, please make sure you have:
./gradlew connectedAndroidTest(or./gradlew testLab) and confirmed all checks still passDateFormatsTest