-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Messenger] ease testing and allow forking the middleware stack #31204
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
Conversation
b38a927
to
3bdf4b0
Compare
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.
I played with this - works really nicely to solve the problem of a middleware calling handle()
multiple times. The middleware needs to know they should clone the stack, but I think that's not a huge issue.
return $this->iterator = null; | ||
} | ||
|
||
return $this->stack[] = $this->iterator->current(); |
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.
I had to stare at this for a minute. When you clone the StackMiddleware
, each clone will still maintain this same, one instance of this MiddlewareStack
, but will now maintain their own StackMiddleware.offset
property (so, that property will move independently). The first StackMiddleware
that uses an item from the iterator will use it, but store it on the stack so that it's available when the other StackMiddleware
asks for that same $offset
.
/** | ||
* @internal | ||
*/ | ||
class MiddlewareStack |
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.
Can't you simply drop the iterator, store middleware as array in StackMiddleware
and advance the pointer manually?
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.
That would defeat laziness, which is a desired property.
…are stack (nicolas-grekas) This PR was merged into the 4.3-dev branch. Discussion ---------- [Messenger] ease testing and allow forking the middleware stack | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | yes | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #31179 | License | MIT | Doc PR | - A less radical alternative than #31185 that preserves laziness and addresses the linked issue. Commits ------- 3bdf4b0 [Messenger] ease testing and allow forking the middleware stack
A less radical alternative than #31185 that preserves laziness and addresses the linked issue.