Missing properties in POST request body

[ChristophSonnleitner]

Hello,

it seems as if the odata-openapi is omitting properties when constructing the bodies for post-endpoints.
I thought I made a mistake, but the issue also persists in the linked TripPin swagger ui:
https://petstore.swagger.io/?url=https://raw.githubusercontent.com/oasis-tcs/odata-openapi/main/examples/TripPin.openapi3.json#/Airlines/post_Airlines

Request-body should have Name and AirlineCode, but only Name is generated in the openapi json-file.

[ralfhandl]

Hi @ChristophSonnleitner,

The $metadata snapshot in this repo has AirlineCode annotated as read-only:

odata-openapi/examples/TripPin.xml

Line 78 in 1beb887

<EnumMember>Org.OData.Core.V1.Permission/Read</EnumMember>

So it is omitted from the create request body.

Maybe the snapshot no longer matches the deployed service.

Will check later whether this snapshot is outdated.

Thanks for reporting this!

[ChristophSonnleitner]

Thank you for your quick response.
The xml that is currently returned by http://services.odata.org/V4/TripPinService/$metadata also still contains the same definition for Airline/AirlineCode.

So maybe the Odata tutorials metadata.xml of TripPinService too does not align with its deployed service anymore?

What I don't quite understand is how the ready-only permission (which omits the property from the post-request-body) plays together with the Nullable=false flag in AirlineCode. (I am new to OData)

[ralfhandl]

What I don't quite understand is how the ready-only permission (which omits the property from the post-request-body) plays together with the Nullable=false flag in AirlineCode.

Yes, that is fishy. We'd have to ask the unknown owner of that API what they intended with this annotation.