-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge next
into master
#5536
Merge next
into master
#5536
Conversation
… importing settings
Run `master` CI jobs on `next` as well
Remove ability to set Google account as server
…2023.2 Dependency updates v2023.2
Add notes about regression testing process
Bumped the targed sdk version
Remove untested and (believed to be) unnecessary updateAnswersForScreen calls
Improved scheduling auto-send jobs
e0b3b39
to
af19f11
Compare
Add tests for save points
@@ -56,27 +55,6 @@ class GoogleDriveDeprecationTest { | |||
.assertText(R.string.google_drive_deprecation_message) | |||
} | |||
|
|||
@Test | |||
fun bannerDisappearsAfterSwitchingFromGoogleDriveProjectToOdkServer() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test is no longer relevant.
@@ -21,7 +21,7 @@ object Dependencies { | |||
const val androidx_multidex = "androidx.multidex:multidex:2.0.1" | |||
const val androidx_preference_ktx = "androidx.preference:preference-ktx:1.2.0" | |||
const val androidx_fragment_ktx = "androidx.fragment:fragment-ktx:${Versions.androidx_fragment}" | |||
const val android_material = "com.google.android.material:material:1.8.0" | |||
const val android_material = "com.google.android.material:material:1.7.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like there is a problem with MaterialCardView
using a Material 3 style with a non-Material 3 theme that we need to address to upgrade to 1.8.0
We end up with a merge commit (from
master
back intonext
) to make this all work, but I think that's better than rebasing so that we don't change commit SHAs and clobber any useful links between commits and PRs. The most important thing to review is the merge commit itself.