Development of the Hydra OpenAPI Parser - v2 #22
Merged
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.
Checklist
Description
/parsers
and/processors
Parsers
are responsible for parsing the text of the OpenAPI Spec and extracting relevant information for creating a Hydra ObjectProcessors
then use this information and act as an adapter to thehydra-python-core
which then convert it to a Hydra ObjectAPIClassProcessor
to finally create a relevant Hydra Class along with the other relevant "metadata" using theAPIInfoProcessor
and then sending it to theOpenAPIDocParser
which assimilates everything to create aHydraDoc
This PR addresses a lot of the open issues in this project currently (#21 , #4 , #19) and is inspired by the Swagger Parser heavily.
Future improvements:
hydra-python-core
Schema
Objects and JSON pointers.