Move middleware::from_fn into axum
#719
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jplatte
reviewed
Jan 24, 2022
jplatte
approved these changes
Jan 25, 2022
auto-merge was automatically disabled
January 25, 2022 09:13
Rebase failed
davidpdrsn
added a commit
that referenced
this pull request
Feb 22, 2022
* Move `middleware::from_fn` into axum * changelog * fix feature * Rephrase changelog a bit
davidpdrsn
added a commit
that referenced
this pull request
Feb 22, 2022
* Move `middleware::from_fn` into axum * changelog * fix feature * Rephrase changelog a bit
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been very happy with
axum_extra::middleware::from_fnso for 0.5 I think we should move it into the main axum crate.Also renamed the type from
MiddlewareFntoFromFnto match std'sstd::iter::FromFn.