We want to add one more Angular widget to Core Apps that displays information about appointments… but those of Bahmni Appointments. Meaning that it will leverage this backend: https://github.com/Bahmni/openmrs-module-appointments
This will most likely mean that Core Apps will become ‘aware of’ Bahmni Appointments and that there will be at least a conditional bean hanging somewhere. This widget will not be configured to show up by default, only if implementers decide to make it appear on their dashboards.
Would you be ok with this code to live in Core Apps?
@mksd I do not see an issue with that however I would like to suggest that you add an issue for a feature harvest for the specific end-point and functionality into the OpenMRS appointment module that way the aware of is temporary
@ssmusoke so you see an issue However what is it? ‘Aware of’ is specifically a non intrusive pattern.
We want everything in one place, in which case Core Apps looks like the most natural and convenient host.
We can’t put it in the ASUI module, it will not be used, nor will be AS. Alternatively we could put it in the Bahmni Appointments module, but this was not a preferred option because we wanted to keep that module backend-only (like AS is basically).
Not really an issue, my suggested approach is make it work today, but plan to remove the dependency over time as the Bahmni appointments should eventually be harvested out of existence
However what is it? ‘Aware of’ is specifically a non intrusive pattern.
