Swagger doesn't work well with || operators #165
Description
This can be observed via broken swagger docs for routes that have such definitions. This brings me to the important question: does the || logic serve a real purpose or is it just a cool trick? I'm pretty pleased to be able to do it, but most of the examples I can think of are highly contrived. That would be fine except it brings significant additional complexity, thus this bug.
Do any of the rho users actually use the || path logic? I know one of our most heavily invested users didn't even know it existed.