Ian

> but I'm still not seeing Amylase under Tests orderability in dev3 It's under `Bloodwork`. The e2e tests only use the [default values](https://github.com/openmrs/openmrs-esm-patient-chart/blob/0c923b72d84f92616fa867f6c134fb66f8cdfd4a/packages/esm-patient-tests-app/src/config-schema.ts#L18), IIRC.

> still, wouldn't amylase be under all orderable tests? It's not in that concept set hierarchy, so, no it wouldn't. Not sure why but Amlayse is just part of the...

> is there still something blocking this? The metadata for "All Orderable Tests" doesn't get loaded correctly, so this fix would probably just cut down on the number of visible...

Actually, no. I called the branch breaking because I thought it would be, but this should actually be backwards-compatible (once I fix whatever is causing the failures there).

> Will the feat() PR title result in this being applied as a minor rather than major change? Well, we version things manually, but as-is, this is currently backwards-compatible with...

> Is there other code outside of preloadImport that relies upon window[slugifiedPackageName]? That and `importDynamic`. This falls into the "gory details" we try to confine to core. The definition of...

@jwnasambu I also see empty state components in patient-search and bed-management. Not sure if those also need to be updated?

I'm actually going to take the opposite view @mseaton took above. I think we _should_ just create the 2.5 omod and go from there. Two reasons: 1. We either need...

Code-wise, I think we're better-off exposing the `formFieldNamespace` and `formFieldPath` properties directly rather than the `formFieldAndNamespace` property for parity with the existing Obs resource, which also exposes them as two...

@wikumChamith Missed this part; are you able to reproduce the test failures locally, because I can't (from master), which makes them hard to track down...