This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
Format mostRecentDateAtRiskLevel in seconds, not milliseconds (EXPOSUREAPP-5239)
#2415
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
d4rken
added
maintainers
ralfgehrer
previously approved these changes
Feb 18, 2021
mtwalli
reviewed
Feb 18, 2021
...ronawarnapp/datadonation/analytics/modules/exposureriskmetadata/ExposureRiskMetadataDonor.kt
Outdated
Show resolved
Hide resolved
…tRiskLevel-timestamp
…tRiskLevel-timestamp
|
Kudos, SonarCloud Quality Gate passed! |
ralfgehrer
approved these changes
Feb 19, 2021
ralfgehrer
deleted the
fix/5239-analytics-mostRecentDateAtRiskLevel-timestamp
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adjusted spec: Format
mostRecentDateAtRiskLevelin seconds, not milliseconds.(See ticket)