-
Notifications
You must be signed in to change notification settings - Fork 13
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
Any plans to support OpenSpec 3.0? #29
Comments
Hi, thanks, that's been a plan for a while now, but currently struggling for time, so I would imagine it would be a couple of months away at least unfortunately. |
+1 on support for OAS 3.0! |
Figured out a solution for the meantime @bengro!
Then in your
Then also add this before your
|
Nice one, @jhodges10 👍 ! I wrote my own gatsby plugin because we rely on OpenApi Spec 3.0 features (hence transforming to OpenApi Spec 2.0 wasn't an option). Unfortunately I cannot share the code as it's closed source, but here the gist for peeps in a similar situation. The hardest part was building the GraphQL model correctly, which is shown here:
The parsing of the spec is delegating to |
We're migrating from 2.0 to 3.0 and we really like this plugin. Are there any plans to support OpenApi Specification 3.0?
The text was updated successfully, but these errors were encountered: