Implement reset_middleware in Server #855
Open
Conversation
This file contains hidden or 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
mdtusz
reviewed
Nov 25, 2021
| assert!(res.header("X-Root").is_none()); | ||
| assert_eq!(res["X-Foo"], "foo"); | ||
| Ok(()) | ||
| } |
There was a problem hiding this comment.
A test should be added to ensure that previously defined routes on the app (i.e. those before line 136) still use the initially set middleware.
|
I'm not a maintainer, but lgtm! |
|
@Fishrock123 do you think it's worth getting this in to include in the v0.17 realease? |
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.
Fixes #850
I implemented reset_middleware in Server according to
#850 (comment)