(fix) O3-3274: Fix failing expressions

[arodidev]

Requirements

• This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes a conventional commit label. See existing PR titles for inspiration.
• My work conforms to the OpenMRS 3.0 Styleguide and design documentation.
• My work includes tests or is validated by existing tests.

Summary

This PR introduces a fix for failing expressions within the forms' engine.

Screenshots

Related Issue

https://openmrs.atlassian.net/jira/software/c/projects/O3/boards/37?assignee=712020:381d2aac-e89b-44ab-803b-02445824ad47&selectedIssue=O3-3274

Other

[arodidev]

@samuelmale the CI disallows importation of the entire lodash module, is there a way around this?

[samuelmale]

@samuelmale the CI disallows importation of the entire lodash module, is there a way around this?

In as much as there is probably a way to dynamically import lodash, I think it's overkill and maybe unnecessary.

Question: Do we really need the entire library? Is that what's happening in AFE @ibacher @denniskigen?

I've done a quick search in Ampath's config repo, and seems like they're mainly consuming lodash's isEmpty(...) utility function;

Should we rather aim for a synthetic version of the lodash object?

import { isEmpty, filter, find } from 'lodash-es';

const _ = {
  isEmpty,
  filter,
  find,
};

[arodidev]

@samuelmale I updated the PR with due changes.

[samuelmale]

We actually may not need these two

[samuelmale]

@arodidev does this fix all the errors related to expressions even for the "Adult Visit Return" form?

[arodidev]

@arodidev does this fix all the errors related to expressions even for the "Adult Visit Return" form?

@samuelmale this addresses majority of the failing expressions(related to lodash). There are a few failing while referencing field ids, will investigate and address those separately.