Incorporate "rest" and "openapi" functions into "openapi" #818
Assignees
Milestone
Comments
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
ricardozanini
added a commit
to ricardozanini/sw-specification
that referenced
this issue
May 10, 2024
…duce HTTP functions Signed-off-by: Ricardo Zanini <zanini@redhat.com>
9 tasks
ricardozanini
added a commit
to ricardozanini/sw-specification
that referenced
this issue
May 10, 2024
…duce HTTP functions Signed-off-by: Ricardo Zanini <zanini@redhat.com>
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
cdavernas
added a commit
that referenced
this issue
May 15, 2024
Fix #818 - Merge REST and OPENAPI operations, introduce HTTP functions
cdavernas
pushed a commit
to neuroglia-io/serverless-workflow-specification
that referenced
this issue
May 21, 2024
…duce HTTP functions Signed-off-by: Ricardo Zanini <zanini@redhat.com> Signed-off-by: Charles d'Avernas <charles.davernas@neuroglia.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be added:
Since we introduced
restoperation type as a shortcut to embed the OpenAPI definition within a workflow, instead of having a different type we can incorporate it into theopenapitype.In practice, we will have a function that can link to an OpenAPI file or have the operation described directly via the
pathsOpenAPI Schema object.Why is this needed:
See the discussion here: #817
The text was updated successfully, but these errors were encountered: