(fix) Allow modifying the visit date to accommodate the new encounter date on all encounters tab #1184
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
|
Hi @ibacher, please have a look at this PR when you have some time. |
|
@ibacher could you please review this PR as it is quite urgent for our users? Many thanks for your help cc @icrc-psousa @icrc-fdeniger @gracepotma |
ibacher
approved these changes
Jun 10, 2023
|
Done. Sorry for the delays. I’ve been at a conference. |
|
thank you so much @ibacher ! |
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.
Requirements
Summary
Visit start/stop dates weren't being passed to form entry engine when editing an encounter from the "All encounters" tab on visits widget. This caused issues when editing the encounter date if it fell outside the designated visit range.
Screenshots