JSS Raxa is about to go into a big front-end development phase. During
this time, it is liable to need REST interfaces with some tables which have not
yet been carried forward in the REST module or in the module which defines
them, and certainly some custom queries and/or representations. It will need
these on a schedule which fits into its front-end development pace. I
anticipate that JSS Raxa will build a helper module to contain those elements
which don't exist in OpenMRS.
What I'd like to discuss is how this work should be coordinated with
OpenMRS. Should we create OpenMRS tickets for all this work? for work that we
think should be incorporated into OpenMRS? for none of this work? Is there a
release schedule with which we can coordinate? Would you rather that the
helper module have its own pseudo-resource or that it extend and override
resources using the @Handler order parameter?
Any thoughts or suggestions would be appreciated. @Jeremy, did you
encounter any similar issues using REST?
_________________________________________
To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
lists...@listserv.iupui.edu with "SIGNOFF openmrs-devel-l" in the body (not
the subject) of your e-mail.
[mailto:lists...@listserv.iupui.edu?body=SIGNOFF%20openmrs-devel-l]
