Bug report - OpenAPI 3 file marked as valid but Read mode shows Page Not Found

[DawMatt]

Hi,

I imported the attached OpenAPI 3 YAML file into v4.8.1.

Read Mode shows "Untitled Hub" and "Page Not Found". Code Mode shows OK but offers no advantage over the text editor I was previously using for OpenAPI editing. Stoplight tells me the spec is valid so I would appreciate the help resolving this issue.

Tested on Windows 10 and Mac desktop clients, and also the web version. Same result.
Example API.yaml.zip

Thanks, Matt

[tbarn]

Hey @DawMatt could you show how you have the Hub setup? Specifically the "Page Settings"

Like this:

[DawMatt]

Hi,

My settings are the defaults. I haven't changed anything re My Hub.

I also couldn't find the settings you are looking for. Please let me know specifically where to find these if you still want them and think I can access them.

I've attached a screenshot of the UI visible when this file has been imported. Essentially the UI appears broken after importing the file. Nothing appears in the documentation/My Hub area.

When I import the file I do select the "import as OpenAPI 3" option.

Thanks, Matt

[tbarn]

Oh okay. I misunderstood where you were seeing the page not found error. I've looked into the OAS3 document you have uploaded and there definitely seems to be some kind of a bug here. We'll need a bit of time to investigate to see what might be going on.

[linas-ipxo]

Hi. I stumbled upon this myself just now.

Through some quick testing, i found out that it fails to display anything if there's a securityScheme defined with type oauth2 in /components

changing the type to whatever invalid string, oauth2sss, fixes the output in Read page

[DawMatt]

Thanks @linas-hef ! Adding "_workaround" to the end of "oauth2" in the securitySchemes area of the file means I can at least view it in read mode now. Great tip, and hopefully will help them track down the issue. Updated example attached, and if you remove the "_workaround" text from the end of the oauth2 statement will break read mode in the current version of Stoplight.
OAS3 Read Mode-ExampleAPI-workaround.yaml.zip

[tbarn]

A fix for the original problem should be going out in the next release. Once the release is out, I'll check in to see if it is fixed on your end.

[tbarn]

Hey @DawMatt, there was a fix for this in the latest release. Are you still having the issue?

[DawMatt]

Hi @tbarn,

I just downloaded and installed to try this out. The issue is kind of not fixed.

I have both the original file and the workaround version of the file (see earlier in the thread) present in the same testing project. So I tried the following steps:

1. Open project
2. Click on the problematic .oas file in the modeling section.
3. Click on the workaround .oas file in the modeling section.
4. Click on the problematic .oas file again in the modeling section.

At step 2 it displays correctly. At step 4 I'm shown a "Darn! Something went wrong!" dialog. Apparently the team has been informed. When I hit the "reload" button the file displays again correctly. So there still seems to be something flaky with the OpenAPI v3 handling..

Update: I've just tried clicking around in the view (e.g. clicking the entry for one of the models in the OAS file) and I immediately get the "Darn" dialog again. Sorry but I'm not revising this to "not fixed". You basically can't interact with the file at all

Thanks, Matt

[tbarn]

Hey @DawMatt, can you send an email into support@stoplight.io? So we can make sure we are looking at the same files in your project and chat more. Reference this GitHub thread and I'll hop onto to our Intercom chat.

[DawMatt]

Thanks @tbarn . Email sent, along with some more details about exactly how I reproduced the issue.