You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should it be more customizable? I mean I think the ordering matter and simply appending generated middleware might not be viable. My suggestion is, perhaps the user control the list of middleware directly through duct.reitit/middleware:
Right now, here how duct.reitit creates middleware:
The ordering of default-middelwares as well as the marge of coercion-middlewares should may be defined by the user like
{:duct.reitit/middleware
[:logger-request-middleware:environment-middleware:parameter-middleware:format-middleware; should do nothing if muuntaja isn't activated :exception-middleware:coerce-request-middleware; should do nothing if coercer is nil or coercion isn't activated :coerce-response-middleware; should do nothing if coercer is nil or coercion isn't activated :user-defined-middleware;; located in `project-ns/middleware/user-defined-middleware
user-defined-middleware ;; symbol located in `project-ns/middleware/user-defined-middleware
]}
The text was updated successfully, but these errors were encountered:
Should it be more customizable? I mean I think the ordering matter and simply appending generated middleware might not be viable. My suggestion is, perhaps the user control the list of middleware directly through
duct.reitit/middleware
:Right now, here how
duct.reitit
creates middleware:The ordering of
default-middelwares
as well as the marge ofcoercion-middlewares
should may be defined by the user likeThe text was updated successfully, but these errors were encountered: