-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Key fields not required #316
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A test case with this annotation would be nice. Could be an existing one with the annotation added, I think we have enough "non-computed" key properties in the examples 😎
|
This is correct, but someone might miss this only possibility to mark a field as "required" in the create structure. The correct way to do that would be via What I am trying to express: this correction may disappoint some users, and there is no mitigation. |
That's for the future phase (#291): odata-openapi/tools/V4-CSDL-to-OpenAPI.xsl Lines 1532 to 1540 in 31b8315
|
Currently, non-computed key properties are required in OpenAPI. But this ignores the case of key properties that can be either provided or omitted (in which case they are computed by the server).
We have three types of key properties
-create
schemaCore.Computed
Core.ComputedDefaultValue
This pull request corrects the OpenAPI description for the second type.