-
Notifications
You must be signed in to change notification settings - Fork 2
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
openapi 3.1.x support #2
Comments
Yes, that's planned :). Are there any features that should be prioritized in your opinion? As always, contributions are very much appreciated! Feel free to open a pull request if you have any changes :). |
Priority would be to use existing 3.0 snippets when editing 3.1 spec. :) |
So I began working on supporting or rather migrating to 3.1.x. As it seems, they introduced a lot of breaking changes and also changed their used json schema. This introduces some challenges, because VS Code does not seem to support needed features of said json schema. So long, we're stuck here, as I don't want to validate the files myself but instead rely on VS Code. BTW according to their release notes they should support newer json schema drafts, but it still won't work. That's a bummer. I opened a SO question, maybe some other people have experienced a similar issue. If there are no answers, I will open an issue on VS Code. |
Issue in VS Code: microsoft/vscode#155379 |
Cool extension.
Will it support 3.1?
The text was updated successfully, but these errors were encountered: