This line was removed.
This word was removed. This word was added.
This line was added.

Changes (1)

View Page History
* We likely need a "render" or "view" event in the Application that triggers following the "dispatch" event.
* The callback on the "route" and "dispatch" events that looks for a returned response should likely also look for View\Model objects, and halt execution.
* Several folks have commented that a "convenience" listener should be introduced to allow returning arrays from controller actions. In such cases, this listener would auto-determine the view script based on controller and optionally action (normalising them following a single, well-documented convention), and marshal a generic ViewModel instance with the returned array and the discovered view script name. This would most likely be implemented as a listener on Zend\Stdlib\Dispatchable, and would have to be explicitly enabled in your application.
* We likely need some convenience around specifying default renderer options for ViewModel instances. As an example, if you plan on using layouts, you shouldn't need to inject the "enable_layout" option every time; additionally, there should be an easy way to specify the default layout. (The latter is done in the DefaultRenderingStrategy currently.)