fix: Ensure proper resolution of $ref references in path parameters #61
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.
Problem Description
The
openapi-extract
tool does not currently copy the contents of#/components/parameters/<param_name>
when a$ref
is used at the#/paths/<path>/parameters
level.Steps to Replicate the Problem
Using the following OpenAPI specification: PagerDuty API Schema.
Run the command:
This results in
#/components/parameters/id
being referenced but not correctly copied into the final spec'scomponents
block.Solution
This patch adds a
deref(...)
call after cloning the path parameters block. This ensures that the$ref
references are properly resolved, resulting in a valid and complete spec file.