More than one Swagger UI doesn't render in specified containers

[quii]

If you attempt to initialise more than one SwaggerUI on a page, it incorrectly renders everything into one container div.

The reason of this seems to be there is some kind of code which is generating a ul element with an id of 'resources'. This is then used to insert the UI into it so when you call SwaggerUI more than once it all gets appended to the first element it finds on the page, rather than the respective one it should go in.

[Isnogud77]

I just experienced the same issue and tried your patch, but it didn't work for me. Could you maybe show how a second SwaggerUi would be initialized? Maybe I'm doing something wrong.

[fehguy]

I haven't personally worked with more than one swagger-ui instance on a page. It seems best to reload the UI when switching. There will be issues with authorization configurations being shared as well, since they're attached to window. So I have to suggest that this is best not done with current swagger-ui implementation.