Ian

My preference here would be to actually merge in the Iniz PR for this domain, so I can remove the metadata completely from the Liquibase scripts.

@dkayiwa That was definitely a risk with this PR, but getting on XStream whitelisting seemed like a must-have. The error on the qa-refapp seems to be this: ``` WARN -...

[Here's a PR that should fix the issue with the EMRAPI part of things](https://github.com/openmrs/openmrs-module-emrapi/pull/240).

It's a flaky test... Or at least, the commit you point to only updates the README.md file, so I'm not certain how that could change test results.

The first of those errors is why every `declarations.d.ts` file has this line: ```ts declare module '*.scss'; ``` That makes the TS compiler happy. The second one is probably one...

Alright, so we had that commit that moved the ambient declarations from the styleguide into the framework. By adding that _explicitly_ to the includes, it appears to fix the TS...

> Are we deprecating registerWorkspace? Yes. The workspace registration via routes.json is basically an improvement in almost every way. > And can we update the [naming conventions](https://o3-docs.openmrs.org/docs/coding-conventions#naming) in the docs...

Seems doable without even hardcoding the UUIDs per se, just changing how we load the order configuration to something like: `/ws/rest/v1/orderentryconfig?v=custom:(uuid,display,names:(display,conceptNameType,locale))`. That will get you all the concept names (unfortunately,...

> consider adding BID as a short name in the twice daily concept ? I mean, it makes sense to me. We probably need to talk to Andy about this,...

What about using `?v=custom:(uuid,display)`. Still requires two calls (one to get everything else, then one to get the concepts for `orderFrequencies`)... I'm inclined to think that this should be reported...