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

Bug Report: datacapture 1.1.0 - read-only mode renders empty questionnaire fragment #2446

Closed
reinhild-merz opened this issue Feb 21, 2024 · 3 comments · Fixed by #2453
Closed
Assignees

Comments

@reinhild-merz
Copy link

Describe the bug
In new datacapture library (version 1.1.0) read-only mode for questionnaire isn't working correctly. When adding this setting to the builder (setIsReadOnly(true)) Questionnaire Fragment doesn't show the questionnaire.

Component
datacapture 1.1.0

To Reproduce
This issue can be replicated in Demo app by setting read-only mode in the QustionnaireFragement builder in the EditPatientFragment
After adding the mode:

  1. Run the demo app
  2. Click on "Patient List"
  3. Click on any patient in the list
  4. Click on "Edit Patient"
  5. Observe no questionnaire rendered

Expected behavior
As in previous(1.0.0) version of the lib, read-only mode should render questionnaire and responses (if provided) in a non-editable fashion.

Screenshots
image

Smartphone (please complete the following information):

  • Device: Pixel5 emulator
  • Android version: 12

Would you like to work on the issue?
No

@santosh-pingle
Copy link
Collaborator

Issue #1829 may have introduced this issue.

@santosh-pingle
Copy link
Collaborator

@reinhild-merz Can you verify if #2453 fixes the issue?

@reinhild-merz
Copy link
Author

@santosh-pingle yes, #2453 worked well for me

@github-project-automation github-project-automation bot moved this from New to Complete in Android FHIR SDK Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Complete
Development

Successfully merging a pull request may close this issue.

2 participants