"No OpenAPI file selected"

[misterspeedy]

I am seeing "No OpenAPI file selected" on the OpenAPI extension panel, even though an OpenAPI file (json or yaml) is open and the folder is trusted.

This seems to be a similar issue to: #125.

The difference from that issue is that if I click "New OpenAPI File" this does successfully create a new file in an unsaved tab, and the extension works correctly for that file. If I save that file with the default content and re-open it, the extension continues to work.

However if I then paste the contents of some other, preexisting OpenAPI file into the recently created, default content file, the extension stops working and the "No OpenAPI file selected" message is shown again.

Version info:

Version: 1.71.1 (user setup)
Commit: e7f30e38c5a4efafeec8ad52861eb772a9ee4dfb
Date: 2022-09-08T19:56:36.424Z
Electron: 19.0.12
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: No

Extension version:

4.13

I haven't tried disabling other extensions but can do so if it would help isolate the issue.

[ak1394]

Could you share contents of one of your preexisting files?

[sharddith]

For me this issue got resolve when I changed openapi: "3.1.0" to openapi: "3.0.0"

[misterspeedy]

It's likely that the issue I had was the same as @sharddith saw, with thanks to them.

[jmcaracoche]

I have the same issue. Looks like the extension doesn't support openApi 3.1 spec yet. Weird as the standard has been published almost a year ago.

[martvyoo]

I had the same issue
OpenAPI 3.1 isn't supported, although it seems to be in the works, but there is no activity
#110

[ak1394]

I've mentioned in #110 that we depend on JSON Schema draft 2019-09 support in VS Code, which is being tracked here: microsoft/vscode#98724

There has been no updates there since November 2022, hence no update on our side as well.

[zyzz15620]

For me this issue got resolve when I changed openapi: "3.1.0" to openapi: "3.0.0"

thanks you sir this works @sharddith