Simon Praetorius
Simon Praetorius
We just discussed this internally: We're currently unsure if this would cement the connection between the "PHP world" and Fluid templates too much. However, we're still open to the idea...
In the long term, the abstract ViewHelper classes `AbstractConditionViewHelper` and `AbstractTagBasedViewHelper` should implement `ViewHelperInterface` directly and avoid extending the "god class" `AbstractViewHelper`. To achieve that, we need to move unnecessary...
From a TYPO3 point of view, things are pretty simple: If you use the latest patch-level version, you get the following Fluid versions: * TYPO3 v14: will be latest Fluid...
@linawolf Should we maybe add a page/section to the TYPO3 docs listing the TYPO3+Fluid version pairings and then link to that page from all relevant `versionadded` sections?
Hi! I think it should be possible to implement this with the current APIs: * set `additionalArgumentsAllowed()` to `true` in your component collection (I assume you already do that) *...
> We were not yet using a Custom Component Renderer because we thought that might block or complicate future updates. Not the `ComponentAdapter` (which shouldn't be replaced), but the `ComponentRenderer`...
Related: #1135
I can see some use cases where this might be helpful, similarly to JSON formatting. I think it doesn't hurt to add this to Fluid, since it's a fairly simple...
Or you leave it in but don't set a default and remove the brackets if it isn't set. Not sure which one is better.
Thanks! Just some small adjustments, then it can go in. :)