fix(data-integrity): add indicator for slow checks #604
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
|
🚀 Deployed on https://pr-604--dhis2-scheduler.netlify.app |
Birkbjo
commented
Mar 12, 2024
| } | ||
|
|
||
| .transferOption { | ||
| display: flex; |
There was a problem hiding this comment.
I changed this to flex, mostly because I prefer using gap instead of margins for spacing between the header and other stuff.
ismay
approved these changes
Mar 12, 2024
|
🎉 This PR is included in version 101.5.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds an indicator to checks that have
isSlow: true. The new UI inData Administrationseparates these checks completely, because the user should be cautious when running these checks. So I think it's quite important to distinguish those here as well.