You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But one might also be able to show videos or any other kind of property or add a separate handling for integers, booleans, etc.
The current implementation is hard to extend, as no Case object was used.
A new implementation should offer planned extensibility via additional cases that can be added and we should also add renderer for common media types.
Possible Solution
We could either simply turn the current rendering into a case object in which each output type renders a definition list item, or we allow registering custom rendering only for the property value and ensure that the property name is always rendered the same way.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this topic?
Description
Currently the property renderer of the raw content mode only handles inline editables and image interface instances in https://github.com/neos/neos-development-collection/blob/8.3/Neos.Neos/Resources/Private/Fusion/RawContent/NodeProperty.fusion
But one might also be able to show videos or any other kind of property or add a separate handling for integers, booleans, etc.
The current implementation is hard to extend, as no
Case
object was used.A new implementation should offer planned extensibility via additional cases that can be added and we should also add renderer for common media types.
Possible Solution
We could either simply turn the current rendering into a case object in which each output type renders a definition list item, or we allow registering custom rendering only for the property value and ensure that the property name is always rendered the same way.
The text was updated successfully, but these errors were encountered: