Show multiple versions in scalar viewer in a quirky manner

[Docteh]

So for whatever reason, the routing really doesn't like the idea of routing to a single field, like /favicon.ico or /scalar
To work around this, I propose we add some additional routing so that we can access the API documentation at /scalar/viewer so that users can go there and then choose which version of the API they wish to view

Screenshot of what I'm talking about:

[LucHeart]

I'm not sure I understand? Why wouldn't a top level path work?

[LucHeart]

so scalar does support multiple versions with s selector also?

[Docteh]

So if you visit https://api.openshock.app/scalar/ you get this sort of response where it is considering scalar to be a version

{"type":"https://docs.api-versioning.org/problems#invalid","title":"Invalid API version","status":400,"detail":"The HTTP resource that matches the request URI 'https://api.openshock.app/scalar/' does not support the API version 'scalar'.","traceId":"00-5de463b17daaa109d66234e9da0d96b5-8e832d76733ff076-00"}

I did some digging around, and tinkering, if you add routes like this to Program.cs the one for /test also gives an error, specifically test is an invalid version, the other two routes function normally

app.MapGet("/", () => "Hello World!1");
app.MapGet("/test", () => "Hello World!2");
app.MapGet("/test/test", () => "Hello World!3");

For scalar, it does support multiple versions with a selector, downside is that you have to specify which documents to show. Which is done by the two calls to AddDocument. They added it a month ago in scalar/scalar#5029

2025-04-18.12-50-54.mp4