1. I wish the Route filter could take more arguments e.g filter by action, then path, etc: 2. Pipeline is awesome. Could even be: ->finally($this->cleanup(...)) ->then($this->complete(...))
It'd be the same as pipeline is like a builder pattern where you configure the pipeline obj instance and then it runs, so "order of factors does not alter the product"
![Seungmin "그렇게, 천천히, 우리(As we are)" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/kAzmhLHePqU/mqdefault.jpg)
I am a beginner in Laravel, but I love these features and I love how powerful these features can be. Thanks to Laravel Community!
Our pleasure! 🙏 (Christoph)
Thanks!
1. I wish the Route filter could take more arguments e.g filter by action, then path, etc:
2. Pipeline is awesome.
Could even be:
->finally($this->cleanup(...))
->then($this->complete(...))
My intuition is to put ->finally(...) chained after ->then(...) - does it work, or is it automatically ran after, and thus never if ->then() fails?
☝
It'd be the same as pipeline is like a builder pattern where you configure the pipeline obj instance and then it runs, so "order of factors does not alter the product"