Way to disable validator?

[hlubovac]

I've seen Known Issues and the current support for only "url" and "spec" settings. I'm not sure what the "spec" value is supposed to be, but - anyway - I'm not able to load an existing, non-public swagger-2 document (I'm also not sure if loading a v2 spec is a valid expectation), and, based on the feedback within the UI, I'm guessing it might be because the script isn't getting passed that specs-validation step.

I see it working for petstore; the only thing I changed within index.html is the url value. Tried both over http:// and file:///.

Thanks.

[hlubovac]

Strange, but this works - however, randomly/occasionally. What I noticed: when browser's F12 dev tools (or, console) is open/enabled, then this won't work, no matter what. When that tool/console is not present, then this works (not every time, though). I don't know if this is related or a coincidence, but I can't use those client tools to troubleshoot.

[hlubovac]

I just noticed: I still get validator's red "error" icon on the bottom of the UI - so, UI not rendering might not be related to validation failing. Specs url is still local.

[ddelay]

I have the Swagger UI distribution deployed to an internal HTTP server (inside a company firewall). Since upgrading to Swagger UI 3.0.x, I've seen the same behavior. When I try to load a spec from the same internal HTTP server, Swagger UI displays, "No operations defined in spec!" and the validator icon shows an error. The spec is in fact valid. It's just that on-line validator can't reach the spec on the internal server.

This is a regression from Swagger UI 2.2.x. Previously, it would render the spec's operations even when the spec failed to validate.

The work around is to put the spec in a location the validator can reach (for example a Gist). However, I still think this is a defect. We have to be able to load specs from internal servers.

[webron]

Yup, that looks like a bug. You should be able to set as a configuration validatorUrl: null and that should disable it. Regardless, a broken validation should not break rendering of the spec.

[larshp]

also see #2761

[bodnia]

@hlubovac @ddelay fix disable of validator is merged to latest master. When passing validatorUrl other than undefined then validator badge is not shown. In fact this is not related to operations render, as they are separate components.

As per fetching spec url, I tested 3 cases: when index.html is opened as a file in browser, served with our dev server (npm run dev) and build-in simple Webstorm server and passing spec url as config into SwaggerUIBundle and with query parameter both worked. Testing spec was hosted on simple https://www.npmjs.com/package/gulp-connect server with CORS enabled. I wonder if @hlubovac @ddelay you can send me the spec to investigate what may go wrong.

[hlubovac]

I'll send you mine, if you publish your email address (I'd rather not share publicly). Or, ask your 2 colleagues, @fehguy and @webron, to forward you the file that I sent them previously.

[ddelay]

@bodnia, the "No operations" problem appears to be fixed. My comment was about an earlier version of 3.0.x -- one that I was testing at the end of last week. Yesterday, I deployed the latest distribution from master and I am able to load specs from my internal server. Thanks.

[hlubovac]

@bodnia

Got the latest; some feedback on your change:

validatorUrl:null resulted in endpoint info displayed, but the red validator badge was still on the bottom of the page.

validatorUrl: undefined or that setting ommitted resulted in "No operations defined in spec!" message, with the red badge still showing.

So, basically, I don't see improvement. I'm pretty sure that I did update all relevant files ("dist"), and if it's some proof that I did taht, you changed preset configuration in index.html ("SwaggerUIStandalonePreset").

Maybe look for conditions related to showing "No operations defined in spec!" message. I was curious and searched, and I see it's mentioned in "src/core/components/operations.jsx" and "src/core/components/overview.jsx", but I don't understand that ES6 syntax. Maybe there's something wrong within specSelectors.taggedOperations() function that results in empty result mistakenly returned?

Or perhaps some timing issue related to premature processing of yet incompletely downloaded specs file (since the problem appears intermittent)?

Sorry, I can't step through any of the client code because, each time I open F12 tools this always results in same error message". It only intermittently won't work when I have F12 closed. I tried dozens of times.

[webron]

@hlubovac - I've forwarded your spec to @bodnia.