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
While working on gathering requirement for #9 it became apparent that duct.reitit/routes would become hard to read easily.
To solve this potential unwanted complexity in configurations, duct.core/spec-ns should be supported the same way duct.core/middleware-ns and duct.core/handler is.
Users then can define spec for requests and responses like <project-ns>.<spec-ns>/login-user, <project-ns>.<spec-ns>.user/login and then either reference them with a keyword after defining them in registry or reference the symbol directly
The text was updated successfully, but these errors were encountered:
While working on gathering requirement for #9 it became apparent that duct.reitit/routes would become hard to read easily.
To solve this potential unwanted complexity in configurations,
duct.core/spec-ns
should be supported the same wayduct.core/middleware-ns
andduct.core/handler
is.Users then can define spec for requests and responses like
<project-ns>.<spec-ns>/login-user
,<project-ns>.<spec-ns>.user/login
and then either reference them with a keyword after defining them in registry or reference the symbol directlyThe text was updated successfully, but these errors were encountered: