-
-
Notifications
You must be signed in to change notification settings - Fork 435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openapi3: reference originating locations in YAML specs - step 1 #1007
Merged
Conversation
This file contains 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
reuvenharrison
changed the title
Correlate OpenAPI components with their location in the originating YAML spec
Add reference to originating locations in YAML specs - step 1
Sep 21, 2024
fenollp
requested changes
Oct 8, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor edits otherwise LGTM
* Add github.com/pb33f/libopenapi it looks like a reasonable alternative * Update README.md --------- Co-authored-by: Pierre Fenoll <[email protected]>
* fix: issue unmarshalling when discriminator field is set in openapi2.0 * revert original approach * update with different approach * Revert "update with different approach" This reverts commit 2db2b39. * v2 schema with discriminator field set as string * update ref link and comment * run docs.sh
) Signed-off-by: Pierre Fenoll <[email protected]>
fenollp
changed the title
Add reference to originating locations in YAML specs - step 1
openapi3: reference originating locations in YAML specs - step 1
Oct 21, 2024
fenollp
approved these changes
Oct 21, 2024
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 adds the ability to correlate OpenAPI components with the location in the originating YAML spec.
Here's a summary of the changes required to achieve this:
UnmarshalWithOrigin
(see https://github.com/oasdiff/yaml)Origin
struct to OpenAPI components. This requires changes to the UnmarshalJSON functions and, in some cases, replacing native types, likemap[string]string
, by dedicated types that include the original native type and an Origin member.This PR addresses issue #986
Follow up tasks to be addressed by future PRs:
origin
to more elements, namelyComponents
and some types that are unmarshalled withunmarshalStringMapP
orunmarshalStringMap
replace
directives from go.modorigin
to include end line and column and YAML comments as proposed by @fenollp