Simon Praetorius
Simon Praetorius
Currently, the ViewHelper documentation workflow is a bit cumbersome because the JSON file needs to be generated and committed manually. We should check if there are any alternatives that make...
Currently, there are a few ways to influence how the extension embeds assets, both in dev mode and in production. However, while there are quite a few options available, they...
Similarly to the TYPO3 core, the extension should support inlining of assets generated by vite. See #10 and the core patch: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84424
It would be great if the cropVariant for list and detail images could be specified via TypoScript. This would eliminate more cases where the `List/Item` partial needs to be overwritten...
`null` can safely be converted to an empty string, so it's fine to allow it as a base string for string replacement. Resolves: #1279
There needs to be one central place in the documentation where we describe the variable type handling and validation in Fluid, e. g. by ViewHelpers and the `` ViewHelper.
It is already possible to use PHP enums in Fluid templates: Both ViewHelpers and components can define an enum as argument type by using the full name of the enum....
Currently, the changelog in the documentation only covers breaking changes and deprecations. However, the term "changelog" might be a bit too broad here, so we might want to consider renaming...
Similarly to ViewHelpers, there should be a simple way to generate XSD files for components. The solution would probably look something like this: * Introduce new interface `ComponentListProviderInterface` (or similar)...
As an addition to #1109, it should be possible to pass data from the component to the slot. This allows better separation between integration and component when components are nested...