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
Hi there! First off thank you for providing such a high-performance and versatile library, reitit allows one to nicely compose so many ideas from the clojure ecosystem 馃殌
In an effort to have an HTTP server whose execution flow is ridicolously straightforward to understand, I'm trying to achieve a fully interceptor driven server, where each interceptor has one and only one job.
For example the interceptor stack might look like:
exceptions interceptor
format interceptor
default handlers interceptor
routing interceptor
That said, I'm a bit puzzled as to how one is supposed to use the routing interceptor. Below is how I configured the interceptor, but if I try to run it, it rightfully complains that the sieppari executor doesn't have an enqueue method.
Is there a reason why the sieppari executor can't have an enqueue method? If not, would you be happy to accept a PR introducing it?
Hi there! First off thank you for providing such a high-performance and versatile library, reitit allows one to nicely compose so many ideas from the clojure ecosystem 馃殌
In an effort to have an HTTP server whose execution flow is ridicolously straightforward to understand, I'm trying to achieve a fully interceptor driven server, where each interceptor has one and only one job.
For example the interceptor stack might look like:
That said, I'm a bit puzzled as to how one is supposed to use the routing interceptor. Below is how I configured the interceptor, but if I try to run it, it rightfully complains that the sieppari executor doesn't have an
enqueue
method.Is there a reason why the sieppari executor can't have an enqueue method? If not, would you be happy to accept a PR introducing it?
Thanks,
Simon
The text was updated successfully, but these errors were encountered: