-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Define "primary key" for objects #587
Labels
Comments
Tackling PR: #741 |
Yes, I do the same with x-keys. Would be good to have standardized to just "keys" |
Yup, not everything was resolved in #741, and this is why this ticket was not closed. |
@ralfhandl something new there? or should we use an extension ? |
Merged
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OData APIs are based on an entity-relationship model, so the top-level resources are collections of identically structured objects, and there's a subset of properties whose values uniquely identify an object (think: records in a database table).
A similar issue has been addressed in the JSON Schema discussion group, see https://groups.google.com/d/msg/json-schema/CYd8xk1Czyg/XLNxEzDOPj4J
We currently solve this with an extension keyword "x-keys" whose value is an array of strings listing the names of the "primary key" properties.
Anyone else seeing a need for this and wanting to have it in OpenAPI.Next?
The text was updated successfully, but these errors were encountered: