Expose tags, original operation and preprocessing data #303
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.
Hi :)
I'm working on a tool that uses
openapi-to-graphql
internally, and I needed a few minor changes in the source code:tags
from source OAS as part of the operations. This is useful because other OAS tools uses tags.As a side note, a few points to improvement:
extensions
feature (Add 'extensions' to all Type System objects graphql/graphql-js#2097) and keep the OAS metadata as part of the created schema. It will make it simpler to get the source OAS object (instead of trying to guess it from the operation name or field names).lib
to the repo allow developers to be able to install this tool directly from GitHub, but it also causes issues with rebases and merge changed - maybe it could be better to publish alpha version per each commit (we are doing something similar ingraphql-code-generator
repo) instead?Thank you for this tool, it's really helpful, and it's approach really simplifies the integration between GraphQL and OAS :)