Skip to content

Don't fallback to default colors when choice has blank style#7278

Open
seadowg wants to merge 2 commits into
getodk:masterfrom
seadowg:default-colors
Open

Don't fallback to default colors when choice has blank style#7278
seadowg wants to merge 2 commits into
getodk:masterfrom
seadowg:default-colors

Conversation

@seadowg

@seadowg seadowg commented Jun 24, 2026

Copy link
Copy Markdown
Member

Addresses #7265 (comment)

Why is this the best possible solution? Were any other approaches considered?

I've just made sure we always use the Options color unless we a choice has a non-blank value for the relevant color properties.

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?

Just need to check that the issue is fixed! Only the logic that picks the colors for points, lines and shapes has been touched.

Before submitting this PR, please make sure you have:

  • added or modified tests for any new or changed behavior
  • run ./gradlew connectedAndroidTest (or ./gradlew testLab) and confirmed all checks still pass
  • added a comment above any new strings describing it for translators
  • added any new strings with date formatting to DateFormatsTest
  • verified that any code or assets from external sources are properly credited in comments and/or in the about file.
  • verified that any new UI elements use theme colors. UI Components Style guidelines

@seadowg seadowg marked this pull request as ready for review June 24, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant