Fix/resolve bug with source description scoped operation path#138
Merged
DavidAtJentic merged 7 commits intomainfrom Feb 25, 2026
Merged
Conversation
ren-jentic
approved these changes
Feb 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR includes a minor patch relating to
sourceDescription-scoped operationPath resolution in thearazzo-runner.Previously, an
operationPathfield in an Arazzo Description of the form:{$sourceDescriptions.petstoreDescription.url}#/paths/~1pet~1findByStatus/get, which is valid in the Arazzo Standard (see here), would get resolved to the path//pet/findByStatus.This would throw an error, and cause the workflow execution to fail.
With this patch, the paths of this form are now correctly resolved.