Hi Joe! I'm not aware of any versions of Swagger-UI that support this, but if you can point me to an example setup that works, I can look into it further.
You're actually bumping up against a browser security limitation: JavaScript applications are not allowed to access `file://` URLs at all in modern browsers, because otherwise any script would have unfettered access to the local files on your machine. (Allowing such a thing would become a security problem pretty quickly - what if a page grabbed the contents of `file://~/.ssh/id_rsa` for every visitor?) I imagine you're running the service that you're developing while you work with the UI - I'd suggest having your service serve the `swagger.yaml` directly. Many services follow the convention of service the Swagger definition at the root of the API's path (e.g. `http://myapi.com/v1/swagger.yaml`). -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
