Skip to content
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.

Feature/8356 warning on behalf/8980 request #3387

Merged

Conversation

nickguendling
Copy link
Contributor

Description

Introduces the OnBehalfCheckinSubmissionService and implements the actual submission of a checkin on behalf of an attendee that doesn't use the Corona-Warn-App.

Link to Jira

https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-8980

Copy link
Contributor

@NataliaLemmerth NataliaLemmerth left a comment

Choose a reason for hiding this comment

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

UA approved

@@ -53,6 +53,7 @@ final class ClientMock {

var onGetTestResult: ((String, Bool, TestResultHandler) -> Void)?
var onSubmitCountries: ((_ payload: SubmissionPayload, _ isFake: Bool, _ completion: @escaping KeySubmissionResponse) -> Void) = { $2(.success(())) }
var onSubmitOnBehalf: ((_ payload: SubmissionPayload, _ isFake: Bool, _ completion: @escaping KeySubmissionResponse) -> Void) = { $2(.success(())) }
Copy link
Contributor

Choose a reason for hiding this comment

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

sounds a bit strange :D

@@ -152,21 +152,19 @@ class ENAExposureSubmissionService: ExposureSubmissionService {
with: self.symptomsOnset
)

let unencryptedCheckinsEnabled = self.appConfigurationProvider.featureProvider.value(for: .unencryptedCheckinsEnabled)
let unencryptedCheckinsEnabled = AppFeatureProvider(appConfig: appConfig).value(for: .unencryptedCheckinsEnabled)
Copy link
Contributor

Choose a reason for hiding this comment

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

👍

Copy link
Contributor

Choose a reason for hiding this comment

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

This change would not take into account the settings from the dev-menu. Please see the decorater pattern implemented to add the dev-menu functionality. Maybe we should change the pattern. Because its not obvious.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah, thanks for that hint! I've now reversed that change and instead made sure that self.appConfigurationProvider.featureProvider is always up-to-date whenever the app config publisher comes back. Maybe it makes sense to get rid of the AppFeatureProvider(appConfig: appConfig) again as the publisher is now more reliable?

@nickguendling nickguendling merged commit 6573830 into release/2.9.x Aug 23, 2021
@nickguendling nickguendling deleted the feature/8356-warning-on-behalf/8980-request branch August 23, 2021 14:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
task part of a feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants