Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
!!! TASK:
Mvc\Dispatcher::afterControllerInvocation
will not be cal…
…led for CLI requests anymore. Reverts that the cli dispatcher invokes the mvc slots dispatcher slots with cli requests. When there was one dispatcher the slot `afterControllerInvocation` was fired for both cli and web request. (Seemingly only ever at Runtime?) Then with the split of web and cli dispatchers this legacy layer was introduced: cf55b18#diff-2c9408e74a8ac737f84468e74c23956d2057e64196e66b97281905d8697226ca Now during a short time the `Mvc\Dispatcher::afterControllerInvocation` signal was now also called for cli request during compile time. With this bugfix #2529 the initial behaviour was restored again. For cli request it will only fire at runtime, and web request are either way always runtime. This breaking change cleans up the legacy layer. - The original signals Mvc\Dispatcher 'afterControllerInvocation' and 'BeforeControllerInvocation' Will be only invoked for action requests. They still only fire at runtime, as web requests happen at runtime. - The with Flow 6.0 introduced signals Cli\Dispatcher 'afterControllerInvocation' and 'BeforeControllerInvocation' Will still be only invoked for cli requests. Will still fired either at compile or runtime, as cli requests can happen always. In case you used the MVC signals and relied on it to also be invoked for CliRequest, you need to connect as well to the respective Cli\Dispatcher signal. But keep in mind that you might need to check if flow is in runtime as this signal will be also fired for compile time unlike the mvc signal before.
- Loading branch information