-
-
Notifications
You must be signed in to change notification settings - Fork 834
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
Additional Middleware Extender functionality #1971
Additional Middleware Extender functionality #1971
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just ran into the stubbornness of the middleware myself today; having this would be ace! Just noticed it might do with a test?
@luceos I agree that a test would be beneficial however I have zero experience writing them (especially outside of the full laravel Framework) so if I do write test I'll need help from someone who know how. |
I'm fine with doing a test after merging, awaiting the second reviewer. |
Great job, thank you! I agree, we can start work on testing extenders in a next step. IIRC, that was actually my suggestion for your next task. I'd happy to do another round of pairing in order to get this started. 😃 |
I took care of the rebase and squash-merged this. Thank you!!! |
Sorry about not doing it myself, this week at work was crazy (company meetings, remote employees visiting, etc.) |
Implements the remove, insertBefore, insertAfter and replace functionality for middlewares. The IoC container now holds one array of middleware (bindings) per frontend stack - the extender operates on that array, before it is wrapped in a middleware "pipe". Fixes flarum#1957, closes flarum#1971.
Fixes #1957
Changes proposed in this pull request:
flarum.{frontend}.middleware
container to arrayflarum.{frontend}.handler
containerReviewers should focus on:
Confirmed
composer test
).