Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Engage experiment #3353

Draft
wants to merge 84 commits into
base: main
Choose a base branch
from
Draft

Engage experiment #3353

wants to merge 84 commits into from

Conversation

pld
Copy link
Member

@pld pld commented Jun 28, 2024

This is mainly data capture changes, we probably want to close this, open a new PR in https://github.com/onaio/android-fhir/tree/master/datacapture with the data capture changes, cut a release from that, incorporate that release


IMPORTANT: Where possible all PRs must be linked to a Github issue

  • Adds improvements made only for Engage into main

Engineer Checklist

  • I have written Unit tests for any new feature(s) and edge cases for bug fixes
  • I have added any strings visible on UI components to the strings.xml file
  • I have updated the CHANGELOG.md file for any notable changes to the codebase
  • I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
  • I have built and run the FHIRCore app to verify my change fixes the issue and/or does not break the app
  • I have checked that this PR does NOT introduce breaking changes that require an update to Content and/or Configs? If it does add a sample here or a link to exactly what changes need to be made to the content.

Code Reviewer Checklist

  • I have verified Unit tests have been written for any new feature(s) and edge cases
  • I have verified any strings visible on UI components are in the strings.xml file
  • I have verifed the CHANGELOG.md file has any notable changes to the codebase
  • I have verified the solution has been implemented in a configurable and generic way for reuseable components
  • I have built and run the FHIRCore app to verify the change fixes the issue and/or does not break the app

FikriMilano and others added 30 commits August 4, 2023 18:38
Signed-off-by: Elly Kitoto <junkmailstoelly@gmail.com>
Signed-off-by: Elly Kitoto <junkmailstoelly@gmail.com>
Keeping the logs, it's quite useful.
This should be allowed, because an item can be hidden with skip logic, and when it is hidden, the link ID will not be part of the Questionnaire Response item.
By adding link id at the end tag as identifier.
- Only use 1 iteration
- Use regex to find and match tags
- Use index for substitution
- Use StringBuilder to avoid creating new String instances when doing substitution (using kotlin replace)
- Keep using the while loop, as using forEach will skip a character following a replacement (See line 47 in HtmlPopulator class)
@pld pld added the DNM DO NOT MERGE label Jun 28, 2024
Temporary solution, best way is to use rules engine, but rules in root (patient name) cannot interact with the rules in each list item (file name).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DNM DO NOT MERGE
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants