I was wondering how this is solved in modern extensions, but could not figure it out. Most of them just magical using e.g. {data.uid}
inside their views without any $view->assign('data',...)
In my old actions I had used something like this:
public function myAction() {
$data = $this->configurationManager->getContentObject()->data;
$this->view->assign('data', $data);
}
Since getContentObject()
is marked as deprecated in v8, it should be replaced with getContentObjectRenderer()
, but the Configuration-Manager has not such a function.
OK after playing around a while and searching through a lot of classes, it seems that the original solution is still valid, the deprecated message applied to another class which has no meaning in this case:
The Extension File Scanner was miss leading me with its warning, there is no deprecated message inside the logs using this solution,... sorry!