Skip to content

Conversation

@krishna-shrivastav232702

Requirements

  • This PR has a title that briefly describes the work done, including the ticket number if there is a ticket.
  • My work conforms to the OpenMRS 3.0 Styleguide.
  • My work includes tests or is validated by existing tests.

Summary

This PR addresses an issue where the ICRC forms and distress scales were not rendering the object properly. Changes have been made to FormsPage.tsx to ensure that the data is correctly displayed.

Screenshots

Before
Screenshot From 2025-03-27 03-18-10

After
Screenshot From 2025-03-27 03-33-59
Screenshot From 2025-03-27 03-34-04

Ticket URL : https://openmrs.atlassian.net/browse/O3-4574

"jest-environment-jsdom": "^28.1.3",
"lodash-es": "^4.17.21",
"openmrs": "next",
"openmrs": "^6.2.1-pre.2825",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@krishna-shrivastav232702 Is there a specific need for the package updates, or were they introduced unintentionally?

Copy link
Author

@krishna-shrivastav232702 krishna-shrivastav232702 Mar 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, to the best of my knowledge, a package update is needed to resolve the useLeftNavStore issue because the packages automatically changed when i ran the command "yarn up openmrs@next @openmrs/esm-framework@next" please correct me if i am wrong

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it thanks for explaining. However, wouldn't it have been better to address the useLeftNavStore issue separately instead of updating packages together? Just want to make sure we're not introducing unintended changes.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As per the Slack discussions, the fast-data-entry app is broken and should be fixed as part of GSoC 2025. The app is breaking due to missing functions, and the documentation states that this command should be run if any functions are missing. You can refer to this Slack chat: https://openmrs.slack.com/archives/C03U8H2AY/p1742489600215209

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey,@Pratibha0280 @krishna-shrivastav232702 it is best practice to discard the changes that have happened to the yarn.lock file before pushing the pr.

@krishna-shrivastav232702
Copy link
Author

@samuelmale @denniskigen can you please review my PR ??

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants