Fix request body and response representation for ref POST operations

[millicentachieng]

Fixes #228

• Create reference for ref POST operations in requestBodies
• Update schema for ref POST operations to include odata.id
• Update response status code to 204 from 201

POST Operation

Referenced Request Body

Referenced Schema

[irvinesunday]

I think we can also do the same for the RequestBody for ref PUT operations?
cc: @baywet

[baywet]

I know that patch uses the odata bind style on the parent entity. I'm not sure whether put uses odata bind or is straight on the collection like post. Can you recall?

[irvinesunday]

I think we can also do the same for the RequestBody for ref PUT operations? cc: @baywet

(Edited the previous post)

This is the current schema in the RequestBody for ref PUT operations:

We can refactor it out into a reusable component as well and reference it as:

[baywet]

@irvinesunday correct, thanks for catching that, they are essentially the same since the odata type is nullable. To be specific, inserting a new reference in a collection (e.g. a new group member) via POST or updating a single reference (e.g. manager) via PUT takes the same payload. (and both reply 204)

[baywet]

@millicentachieng I believe @irvinesunday was arguing to refactor things so both PUT and POST in the cases we outlined use the same schema component, or did I misunderstand the point?

[millicentachieng]

@baywet PUT and POST reference different schemas.

[baywet]

Thanks for making the changes. Re-reading Irvine's comment I realized he was advocating for a naming convention, not reusing the same schema for PUT and POST. A couple of minor things left.