Skip to content
Snippets Groups Projects
Unverified Commit 66206efd authored by Kolya Opahle's avatar Kolya Opahle Committed by GitHub
Browse files

Risk Calculation does not work because DiagnosisKeysDataMapping is not applied...

Risk Calculation does not work because DiagnosisKeysDataMapping is not applied (EXPOSUREAPP-3895) (#1690)

* We now check for the DiagnosisKeyDataMapping and apply it to the ENFClient if changed

Signed-off-by: default avatarKolya Opahle <k.opahle@sap.com>

* Moved diagnosisKeysDataMapping to windowProvider

Signed-off-by: default avatarKolya Opahle <k.opahle@sap.com>

* Renaming and linting

Signed-off-by: default avatarKolya Opahle <k.opahle@sap.com>

* Moved app config fetch to key provide task, added error handling, added logging to config replace

Signed-off-by: default avatarKolya Opahle <k.opahle@sap.com>

* Fixed old unit tests and implemented tests for config comparison,
TestForAPIFragment is currently broken

Signed-off-by: default avatarKolya Opahle <k.opahle@sap.com>

* Linting

* Added more unit testing for DefaultDiagnosisKeysDataMapper and fixed TestForAPIFragment

Signed-off-by: default avatarKolya Opahle <k.opahle@sap.com>

* Update default app config to latest version

This includes a change for the default for reportTypeWhenMissing from
0 to 1, as 0 is not accepted by setDiagnosisKeysDataMapping.

https://github.com/corona-warn-app/cwa-app-tech-spec/pull/10/commits/090801921f4a8581543a9f716fd0572c12901c71
https://github.com/corona-warn-app/cwa-protocol-buffers/commit/38a641e2a808c41d225e9fd09d27ec7959551412



* Fixed Unittests

Co-authored-by: default avatarMaximilian Lenkeit <maximilian.lenkeit@sap.com>
Co-authored-by: default avatarharambasicluka <64483219+harambasicluka@users.noreply.github.com>
Co-authored-by: default avatarRalf Gehrer <ralfgehrer@users.noreply.github.com>
parent ec88c722
No related branches found
No related tags found
No related merge requests found
Showing
with 302 additions and 27 deletions
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment