@smic IMHO yet another layer to hide logic in. People already put too much logic into the view and view helpers. With data processors, we had yet another layer that would be misused.
However, if someone implements it, I don’t veto on gerrit.
@alexanderschnitzler Do we consider data processors as part of the controller layer or view layer? I had assumed the former and it would feel to me as moving logic out of the view.
@smic I agree. It’s controller logic to me as well but it’s logic that is not part of the controller then and you start searching the logic. Don’t see a reason we need this. Why not use the data processor logic in the controller and make it visible?
@alexanderschnitzler I see. I guess what I’m missing is a universal way to intercept and manipulate the data passed from the controller to the view. That could also be a PSR-14 event in the Abstract controller.
@smic Ok, this is a completely different case to me. Since code is fragmented in this case anyway, I think the best approach would be to implement events and use data processors in event listeners.
@smic btw: my long term goal is to be able to dispatch extbase plugins without typoscript wrapper, directly from a middleware e.g. Introduction of data processors kind of contradicts that idea.
Add comment