Closed
Conversation
Collaborator
Author
|
closed in favor of #16. This PR has a low level control of ordering that we don't want to implement |
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
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.
Description
Adds the following features:
prioritizedecorator that will hoist that middleware as much as it cans. These prioritized middlewares will be executed before any async middleware but always after the schema validatorTest impact
This should be a backward compatible change since the order middleware converter will give the possibilities for middlewares having the $noOrder decorator to provide entities. This is only adding functionality, not removing nor replacing the way middlewares are ordered, it only makes the disposition of middlewares more lax.