Re: [OPENMRS-JIRA] (RESTWS-221) Decide how sub-classes should be handled

classic Classic list List threaded Threaded
1 message Options
Burke Mamlin-2 Burke Mamlin-2
Reply | Threaded
Open this post in threaded view
|

Re: [OPENMRS-JIRA] (RESTWS-221) Decide how sub-classes should be handled

I agree with Ben.  Can we have some of this "subclasses for web services" discussion on the design call so we can more quickly get on the same page?

-Burke

On Mon, Apr 16, 2012 at 10:41 AM, Ben Wolfe (Commented) (JIRA) <[hidden email]> wrote:
Ben Wolfe commented on New Feature RESTWS-221

What is the goal of preventing: POST patient { gender: 'M' } ? Preventing this forces users to know the API more than they should need to. Is it only because we intend to break the patient/person inheritance eventually? DrugOrder will always extend order, so updating Order properties from DrugOrder seems ok.

Why not just leave them as they are in the openmrs api world?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira


[hidden email] from OpenMRS Developers' mailing list