Conversation
JoakimSM
added
the
e2e record
JoakimSM
changed the title
JoakimSM
changed the title
JoakimSM
removed
the
e2e record
|
simonadomnisoru
approved these changes
May 1, 2025
Contributor
simonadomnisoru
left a comment
simonadomnisoru
left a comment
There was a problem hiding this comment.
Looks good to me!
P.S. Excellent findings in this PR, @MatiasArriola!
|
🚀 Deployed on https://deploy-preview-4061.capture.netlify.dhis2.org |
geethaalwan
approved these changes
May 7, 2025
geethaalwan
left a comment
geethaalwan
left a comment
There was a problem hiding this comment.
Tested successfully on 2.39.10 ,2.40.8,2.41.4,2.42.1,2.43 versions
dhis2-bot
added a commit
that referenced
this pull request
May 15, 2025
Contributor
|
🎉 This PR is included in version 102.4.3 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
formsSectionsFieldsUI.I couldn't reproduce the error reported in the newest Capture app (in the versions mentioned in the ticket I could). However, the code was highly error-prone and didn't behave as intended. @MatiasArriola: Thanks for such a thorough description in this PR (EyeSeeTea#4)