@natematykiewicz thanks for the suggestion, I've pushed an update.

It's a little awkward since it needs to be aware of all the potential params which could be passed.

Also, CodeQL still complains 😭

I wonder if the user experience could improved by having latest act as a transparent alias of the latest version to save on needing to redirect?

Alternatively, I wonder if a redirect can be added directly in the router.

Would that help anything? I know there's route constraint classes you can make.

Or maybe a middleware?

I just don't love having to list out all of the possible params. Seems really prone to failure as we add more pages in the future. I understand why you needed to do it (because only permitted params will get returned). That's why I wonder if bringing the controller into this is too far down the line.

Alternatively, I wonder if a redirect can be added directly in the router.
Would that help anything? I know there's route constraint classes you can make.

It's possible, but I expect that would still have the same issues with untrusted URL redirection.

I wonder if the user experience could improved by having latest act as a transparent alias of the latest version to save on needing to redirect?

#1426

I really like the simplicity of #1426, and the lack of a redirect does seem nice.

I'm a bigger fan of current than latest though. Maybe that's because the Postgres docs say "current". I do notice that the Postgres docs don't redirect, which is nice because then all of the links everywhere say "current" instead of "15".