-
-
Notifications
You must be signed in to change notification settings - Fork 45
Pm/master initial merge #2987
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
Pm/master initial merge #2987
Changes from all commits
2518b23
878c09c
c1e6a35
aa616b4
9aa1220
c4a68a6
d78960d
dd05545
acd3aa6
7122c92
63743aa
ede6caf
f145dd6
8b53cbf
1e8dfd3
32d554e
918d1af
90b0c96
66cf541
4f42de2
ab5d325
6c9be03
dbbcfd4
a91d8ab
f51fc58
c7fd1ec
b1e4eff
15cf20a
7198161
d793b9a
aa65ba4
1473e3e
6d0dedb
f207335
c9661f7
cc38e15
50b8a51
66ed0dc
917639f
7860093
1d37be1
c49c22a
55c8b2b
5726518
d6dcfed
b24d580
6deec22
9c88874
2949559
84b2b99
f1c9a26
be1e7f3
f75ba1f
0bc14c9
1fdb815
b060e6f
8323e54
1279ed5
fe9337c
ef38792
7a8288a
81e47cb
6b3cc8d
e8fddc6
c606dca
5b46b0c
98e3291
cde4e2d
7b41370
beb545a
dfac1f9
ec417d8
f2eca90
ed588bd
6f1e556
3fca48f
d3f29f1
b112546
af1b934
cfbf901
2333553
14b063e
bab015c
7530f94
99329d3
89a054f
0e7d208
b73d40e
bd45ea8
bcf637c
630ec83
1a985d8
1fd858f
1f04887
137251a
6b57655
b6668b9
25382c7
a0db6a6
be42905
867c254
78f2e5d
4d1e04b
fdcabfc
a3bd499
23836b6
190cf05
9e0ccf0
329600b
37e9e45
876f0e7
0c7268f
d1c9089
e27a912
b533cc6
df0c184
2cabe0a
c97a152
e0f8beb
635aa5b
61ac361
309db47
8ba5745
5e35022
934c13f
2d2229c
032864c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,29 +1,41 @@ | ||
| ## Summary | ||
| ## Product Description | ||
| <!-- | ||
| Delete this section if the PR does not contain any visible changes. | ||
| For non-invisible changes, describe the user-facing effects. | ||
| --> | ||
|
|
||
| ## Technical Summary | ||
| <!-- | ||
| Provide a link to the ticket or document which prompted this change, | ||
| Describe the rationale and design decisions. | ||
| - Provide a link to the ticket or document which prompted this change. | ||
| - Describe the rationale and design decisions. | ||
| --> | ||
|
|
||
| ## Feature Flag | ||
| <!-- If this is specific to a feature flag, which one? --> | ||
|
|
||
| ## Product Description | ||
| <!-- For non-invisible changes, describe user-facing effects. Would be good to add screenshots/videos for any major user facing changes --> | ||
| ## Safety Assurance | ||
|
|
||
| ## PR Checklist | ||
| ### Safety story | ||
| <!-- | ||
| Describe: | ||
| - how you became confident in this change (such as local testing). | ||
| - why the change is inherently safe, and/or plans to limit the defect blast radius. | ||
|
|
||
| - [ ] If I think the PR is high risk, "High Risk" label is set | ||
| - [ ] I have confidence that this PR will not introduce a regression for the reasons below | ||
| - [ ] Do we need to enhance manual QA test coverage ? If yes, "QA Note" label is set correctly | ||
| - [ ] Does the PR introduce any major changes worth communicating ? If yes, "Release Note" label is set and a "Release Note" is specified in PR description. | ||
| In particular consider how existing data may be impacted by this change. | ||
| --> | ||
|
|
||
| ### Automated test coverage | ||
| <!-- Identify the related test coverage and the conditions it will catch --> | ||
|
|
||
| <!-- Identify the related test coverage and the tests it would catch --> | ||
| ### QA Plan | ||
| <!-- | ||
| - Describe QA plan that (along with test coverage) proves that this PR is regression free. | ||
| - Link to QA Ticket | ||
| --> | ||
|
|
||
| ## Labels and Review | ||
|
|
||
| ### Safety story | ||
| <!-- | ||
| Describe any other pieces to the safety story including | ||
| local testing, why the change is inherently safe, and/or plans to limit the blast radius of a defect. | ||
| --> | ||
| - [ ] Do we need to enhance the manual QA test coverage ? If yes, the "QA Note" label is set correctly | ||
| - [ ] Does the PR introduce any major changes worth communicating ? If yes, the "Release Note" label is set and a "Release Note" is specified in PR description. | ||
| - [ ] Risk label is set correctly | ||
| - [ ] The set of people pinged as reviewers is appropriate for the level of risk of the change |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -44,6 +44,8 @@ dependencies { | |
| testImplementation 'org.jetbrains.kotlinx:kotlinx-coroutines-test:1.7.3' | ||
| testImplementation 'io.mockk:mockk:1.12.7' | ||
| testImplementation 'org.json:json:20231013' | ||
| testImplementation 'org.mockito:mockito-core:5.5.0' | ||
| testImplementation 'org.json:json:20140107' | ||
|
Comment on lines
+47
to
+48
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Duplicate JSON Dependency Versions Detected The new changes introduce a second declaration of the |
||
| testImplementation project(path: ':commcare-core', configuration: 'testsAsJar') | ||
|
|
||
| androidTestImplementation 'androidx.test:runner:1.4.0' | ||
|
|
@@ -109,7 +111,6 @@ dependencies { | |
| implementation 'com.google.firebase:firebase-messaging:21.1.0' | ||
| implementation 'com.google.firebase:firebase-crashlytics:17.2.1' | ||
| implementation 'androidx.legacy:legacy-support-core-ui:1.0.0' | ||
|
|
||
| implementation('com.github.bumptech.glide:glide:4.9.0') { | ||
| exclude group: 'com.android.support' | ||
| } | ||
|
|
@@ -306,9 +307,7 @@ android { | |
| buildConfigField 'String', 'ANALYTICS_TRACKING_ID_LIVE', "\"${project.ext.ANALYTICS_TRACKING_ID_LIVE}\"" | ||
| buildConfigField 'String', 'ANALYTICS_TRACKING_ID_DEV', "\"${project.ext.ANALYTICS_TRACKING_ID_DEV}\"" | ||
| buildConfigField 'String', 'MAPBOX_SDK_API_KEY', "\"${project.ext.MAPBOX_SDK_API_KEY}\"" | ||
|
|
||
| buildConfigField "String", "FIREBASE_DATABASE_URL", "\"${project.ext.FIREBASE_DATABASE_URL}\"" | ||
|
|
||
| buildConfigField 'String', 'CCC_HOST', "\"connect.dimagi.com\"" | ||
|
|
||
| testInstrumentationRunner 'org.commcare.CommCareJUnitRunner' | ||
|
|
||
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.
Wildcard MIME types in
<data>tags.You’re allowing matching of all file types (
"*/*") and schemes. This can be very broad and pose security or UX issues if your app handles unexpected file contents.Also applies to: 107-107