I’d like to work on this in the next couple weeks. Not the generator part (sorry @ibacher ) but rather the integration with
What we have presently is IMO a second SDK,
npx openmrs, which is a very good thing and was definitely the right decision. The task now is to integrate that with the maven SDK.
I agree with @mseaton 's proposals. As @ibacher suggests, I think we should implement this by having the maven SDK delegate to the
openmrs frontend tool as much as possible.
So I suggest that
openmrs-distro.properties should support the following sorts of properties:
# Microfrontends to include, a la microfrontends.json
# The base application path and SPA path
# Paths to config files to build in
# Additional import map lines
# becomes the line "config-file"="assets/another-config.json"
# Additional assets to bundle with the application
Where we have files
assets/another-config.json all in the distro folder.
This will build the specified frontend application to
frontend/ in the application data directory, both in development and when building the distribution. This will work out of the box with
I don’t know how the SDK should support builds where the frontend is being served from outside the application data directory. We should figure this out. @mksrom , @mksd ?
I realize this seems like a lot of new stuff in
openmrs-distro.properties. Other ideas are welcome. But these are all application build parameters and that seemed like the natural place for them to go.
CC @jdick , @corneliouzbett , @dkayiwa