-
Notifications
You must be signed in to change notification settings - Fork 49
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
tools/importer-rest-api-specs
: refactoring the Parser package
#4307
Conversation
tools/importer-rest-api-specs
: refactoring the Parser package
|
||
Where possible we use the terminology `API Definition` since these are implementation details - but this more specific terminology will be used where necessary. | ||
|
||
TODO also mention Supplemental Data |
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.
@manicminer do you have context on this?
5585fc2
to
273f87f
Compare
tools/importer-rest-api-specs/internal/components/apidefinitions/parser/parsingcontext/build.go
Outdated
Show resolved
Hide resolved
tools/importer-rest-api-specs/internal/components/apidefinitions/parser/parsingcontext/build.go
Outdated
Show resolved
Hide resolved
tools/importer-rest-api-specs/internal/components/apidefinitions/parser/parsingcontext/build.go
Outdated
Show resolved
Hide resolved
// if this is a parent model, look for implementations. this will currently only work for children defined in | ||
// the same swagger file. |
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.
Do we handle the case where the children are defined in a different swagger file somewhere else in build.go
?
Context: #3727
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.
Yes, this should get picked up by https://github.com/hashicorp/pandora/pull/4307/files#diff-d2cb55dda7e9facde77a39139c64afb00da29f5f92150f1e9eec14766b11c4b1 (which I think is your original implementation)
f57a3a2
to
23eccdf
Compare
…ers out into the new structure
…a Data Workaround
…e over to using the SDK types/new path This is a copy and patch up, since I want to leave the existing code path as-is for the moment, to break it apart more effectively
… Service/APIVersion
…rkarounds` package
…age into the new structure
…to the new package This wants refactoring, but moving it over allows cleaning the rest up
…kage There's a bunch of these, and whilst these'll get replaced in time with #4017 but for now this cleans this up
…since it doesn't seem to be required for DataFactory models as they use external Swagger Refs.
…licates (avoid parsing the same tag twice)
This reverts commit 31b45ca.
… more explicit" This reverts commit 71a166f.
… `go-openapi/jsonreference`, and `go-openapi/spec`
…resolve all remote references
…L-decoded when parsing from the Ref URL fragment
…pect full ancestry
…ame set of resources
…der when parsing operations, as this was never utilised and leads to skipping resources/operations
d9f992a
to
1da6920
Compare
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.
LGTM 🪀
This PR refactors the Parser package into
apidefinitions
- and removes the old logic/pipelineRight now this mostly works and requires a few fixes around Discriminators/Supplementary Data that @manicminer is going to pick up
Mostly fixes/rounds out #3754