Curious if anyone here knows why reitit.ring/ring-handler accepts :middleware in its options to wrap the resulting ring-handler... Is this just supplied as convenience over including "route-wide" middleware in a top level ["" {:middleware ...} [...]] routes definition?

@jameslintaylor :middleware at the top wrap also the default handler.

Ah, of course! Thanks