Is there any option to load multiple swaggers in SpecUrl

[binobose]

Hi, I am loading the Swagger in the below format,

<RedocStandalone
        specUrl = 'https://....../datafile.json'
        />

can anyone please let me know if there's any option to load multiple Swaggers in this context.

[RomanHotsiy]

You can't load multiple swagger files at once. ReDoc doesn't support this.

Although, you can add some buttons/links/dropdown to change specUrl. Changing specUrl will update ReDoc with the corresponding spec.

You can also provide different specUrl based on the current path and have multiple pages each with the separate ReDoc instance.

Closing this issue.
Feel free to continue the discussion here!

[binobose]

Thanks @RomanGotsiy for the quick response.

[J-Gonzalez]

@binobose - Did you find a clean way to get various swaggers to work? A central source for seeing all documentation for all of our microservices is what we really need. Ability to pass in multiple specUrls would be amazing, but modifying app with dropdown/links also would work fine.

[marcelstoer]

This is a feature request that has come up again and again (search the issues for 'multiple') e.g. #442 or #278. Most of them got closed pretty quickly as out-of-scope. That's why I didn't bother creating another one. I have the feeling at this point not even a PR to that effect would be very welcome.

I agree with @J-Gonzalez that specifying a specUrls attribute would be the sane thing to expect. That's exactly what Swagger UI does:

const ui = SwaggerUIBundle({urls: [{url: "foo.yaml",name: "Foo"},{url: "bar.yaml",name: "Bar"}], etc});
...
window.ui = ui;

[volbrene]

@binobose I have create a docker image which fix your problem: https://hub.docker.com/r/volbrene/redoc

[marcelstoer]

@volbrene Interesting, where's the code to that?

[volbrene]

At the moment the code is in my private gitlab.

[marcelstoer]

Oh, ok. Then this - from your Docker Hub page - is going to be a bit difficult 😜

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

[volbrene]

Huch sorry, I have remove this part. Thanks for this info 👌

[marcelstoer]

Doing the opposite (making the repo public) would have been more helpful...Your choice of course but I would have liked to contribute new features.

[volbrene]

Which feature for example? :)

[marcelstoer]

We obviously don't have the same philosophy with regards to using and creating (open-source) software. This isn't the right place to discuss them. So, never mind.

[davinchia]

@marcelstoer want to share how you ended up solving this issue? running into the same issue right now. @volbrene's solution is fine but i would like to do this with yamls that are not hosted on the public internet, which might mean hacking/building on top of his image

[marcelstoer]

I didn't solve it yet. Doing this with a Docker image is certainly a good approach but building something closed-source around an open-source project certainly isn't.

[davinchia]

@volbrene will be helpful if you can share the code to your image!

[volbrene]

Hello guys, I have public my code: https://github.com/volbrene/redoc Hope it would be helpfull.

[davinchia]

Thanks @volbrene! Do you know if this works with local yaml files? if I package my yamls with the docker image, would that work out of the box?

[volbrene]

@davinchia I will use the offical redoc implementation. It hope this ticket helps: #149