Replies: 2 comments 10 replies
-
I think it would be nice to support this as a configuration option if possible--a second extractor could also work but it would be a shame to introduce a separate extractor just to allow manual loading. |
Beta Was this translation helpful? Give feedback.
-
Couldn't you also work around this by loading the It might even be possible to wrap this all in an extractor of your own that wraps All this is say I think a better approach is to leverage Axum itself a little more as opposed to change this crate. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a middleware that uses the
Messages
extractor, but if a condition is not met the messages are never actually used by the middleware. Since the extractor is callingMessage::load
, the messages are removed by my middleware and never able to be used by further handlers/middleware.It would be nice if there were a second extractor that did not automatically load the messages, leaving it up to the handler/middleware to do so manually. For that to work, the
Messages::load
method would need to be made public.Is this something you'd consider adding or merging if I were to put together a PR?
Beta Was this translation helpful? Give feedback.
All reactions