-
Notifications
You must be signed in to change notification settings - Fork 194
Open
Labels
RespectRelated to the `respect` command which works with Arazzo specificationRelated to the `respect` command which works with Arazzo specificationType: Enhancementp3
Description
Is your feature request related to a problem? Please describe.
It is a rather common mistake in Arazzo specification, when not defined output used in consequent steps.
As expected in this case the Respect run result is an error.
steps:
- stepId: list-events
operationPath: '{$sourceDescriptions.museum-api.url}#/paths/~1special-events/get'
- stepId: create-event
operationPath: '{$sourceDescriptions.museum-api.url}#/paths/~1special-events/post'
requestBody:
payload:
location: 'Under the seaaa 🦀 🎶 🌊.'
dates:
- $steps.list-events.outputs.events.0.dates.0Describe the solution you'd like
Would be beneficial to have build in Rule or Plugin that will allow to validate this type of mistake before the execution.
It is important to check outputs occurrence on different levels, like parameters, payload, .etc. and highlight if it was not previously defined on workflow or step levels.
Describe alternatives you've considered
Do nothing and allow users to fix the errors.
Additional context
Original idea conversation: https://redoc-ly.slack.com/archives/C071H03PDC1/p1748614654088499
Metadata
Metadata
Assignees
Labels
RespectRelated to the `respect` command which works with Arazzo specificationRelated to the `respect` command which works with Arazzo specificationType: Enhancementp3