Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow registration of custom middleware before any middleware #86

Merged

Conversation

lcobucci
Copy link
Member

This allows users to register custom middleware before and/or after the ones provided by default.

To do so, they need to configure the priority of their middleware considering that Chimera will register the default using the following priorities:

  • Content negotiation -> 110
  • Routing + body parsing -> 100
  • All other default ones -> -100

Closes #4

This allows users to register custom middleware before and/or after the
ones provided by default.

To do so, they need configure the priority of their middleware
considering that Chimera will register the default using the following
priorities:

* Content negotiation -> 110
* Routing + body parsing -> 100
* All other default ones -> -100

Fixes #4
@lcobucci lcobucci added the Improvement Improvement of existing feature label Feb 21, 2021
@lcobucci lcobucci added this to the 0.4.0 milestone Feb 21, 2021
@lcobucci lcobucci self-assigned this Feb 21, 2021
We may have some flaky stats since we're running infection against the
functional tests.

This should be resolved once we have more unit tests.
@lcobucci lcobucci merged commit 7c2080a into 0.4.x Feb 21, 2021
@lcobucci lcobucci deleted the allow-registration-of-custom-middleware-before-any-middleware branch February 21, 2021 23:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Improvement of existing feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow mapping HTTP middleware before of any standard middleware
1 participant