Skip to content

Conversation

@grzesiek2010
Copy link
Member

@grzesiek2010 grzesiek2010 commented Sep 16, 2025

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

As usual, I've updated the dependencies for the next release. Nothing special to discuss here.

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 doesn't require testing.

Do we need any specific form for testing your changes? If so, please attach one.

No.

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:

  • 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

@grzesiek2010 grzesiek2010 force-pushed the dependency_updates_for_2025.4 branch 3 times, most recently from abc24b7 to 20b6381 Compare September 17, 2025 10:13
@grzesiek2010 grzesiek2010 marked this pull request as ready for review September 22, 2025 06:48
.append(getString(org.odk.collect.strings.R.string.dont_have_project))
.append(" ")
.color(getThemeAttributeValue(context, com.google.android.material.R.attr.colorAccent)) {
.color(getThemeAttributeValue(context, androidx.appcompat.R.attr.colorAccent)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should be using a Material color here instead of an AppCompat one I think. Same goes for the other places we're using colorAccent.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I replaced colorAccent with colorPrimary as colorAccent does not exist in Material 3 but I'm no longer able to use com.google.android.material.R.attr to access it programatically so it looks like I need to use androidx.appcompat.R.attr.

}
if (accuracyCircle == null) {
int stroke = ContextUtils.getThemeAttributeValue(requireContext(), com.google.android.material.R.attr.colorPrimaryDark);
int stroke = ContextUtils.getThemeAttributeValue(requireContext(), androidx.appcompat.R.attr.colorPrimaryDark);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, we should take the opportunity here to replace this with a Material Color

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed colorPrimaryDark but when it comes to androidx.appcompat.R.attr see above.

@seadowg
Copy link
Member

seadowg commented Oct 29, 2025

@grzesiek2010 just nudging on this in case it's fallen through the cracks!

@grzesiek2010 grzesiek2010 force-pushed the dependency_updates_for_2025.4 branch from 20b6381 to aed52c9 Compare October 29, 2025 13:19
@grzesiek2010 grzesiek2010 force-pushed the dependency_updates_for_2025.4 branch from aed52c9 to 81f1cc7 Compare October 29, 2025 14:00
@grzesiek2010 grzesiek2010 requested a review from seadowg October 29, 2025 14:32
@grzesiek2010 grzesiek2010 merged commit c9fb0db into getodk:master Oct 29, 2025
6 checks passed
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.

2 participants