Introduce HelperPluginManagerInterface
#330
Conversation
In order to have a simple way to reset all state that has built up in view helpers / plugins, the plugin manager overrides `Container::get` to populate a list of stateful plugins that have been used during the rendering cycle. Also re-writes "Advanced Usage", de-emphasising MVC related docs. Signed-off-by: George Steel <george@net-glue.co.uk>
| * Resets the internal state built up in any view helpers so that further rendering cycles are not polluted | ||
| */ | ||
| public function resetState(): void; |
There was a problem hiding this comment.
This is a very welcome addition 👍
|
My plan here is hopefully to drop "Rendering Strategies" and the Plugin Managers don't provide any way to reset/clear built services AFAIK, nor extract config, so that would need to implemented over there first if tearing down the container was the preferred route. |
Co-authored-by: Matthew Weier O'Phinney <matthew@weierophinney.net> Signed-off-by: George Steel <george@netglue.uk>
Signed-off-by: George Steel <george@net-glue.co.uk>
…formance Signed-off-by: George Steel <george@net-glue.co.uk>
|
Anyone have any objections if I merge this? Looks like all feedback is resolved |
|
(I will recheck the documentation before the final release.) |
In order to have a simple way to reset all state that has built up in view helpers / plugins, the plugin manager overrides
Container::getto populate a list of stateful plugins that have been used during the rendering cycle.Also re-writes "Advanced Usage", de-emphasising MVC related docs.