-
Notifications
You must be signed in to change notification settings - Fork 471
Open
Description
In OpenAPI 3.1.0 webhooks are defined as path items, as such, their operations also require an operation id.
None of the webhook operations today have an operation id.
Additionally, none of them have summary, which is also required according to the specification
Here is the list of JSON pointers:
- '#/webhooks/batch_cancelled/post/operationId'
- '#/webhooks/batch_completed/post/operationId'
- '#/webhooks/batch_expired/post/operationId'
- '#/webhooks/batch_failed/post/operationId'
- '#/webhooks/eval_run_canceled/post/operationId'
- '#/webhooks/eval_run_failed/post/operationId'
- '#/webhooks/eval_run_succeeded/post/operationId'
- '#/webhooks/fine_tuning_job_cancelled/post/operationId'
- '#/webhooks/fine_tuning_job_failed/post/operationId'
- '#/webhooks/fine_tuning_job_succeeded/post/operationId'
- '#/webhooks/realtime_call_incoming/post/operationId'
- '#/webhooks/response_cancelled/post/operationId'
- '#/webhooks/response_completed/post/operationId'
- '#/webhooks/response_failed/post/operationId'
- '#/webhooks/response_incomplete/post/operationId'
bigwill69bigwill69
Metadata
Metadata
Assignees
Labels
No labels