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
Is there a reason that fluids property access is slightly different than eels?
In fusion/eel i would also like to call ${fooo.isSomething} which calls the method isSomething() to be more descriptive than ${fooo.something} which feels more like a direct getter and will actually use the getter if defined.
That was brought to fluid as feature but never implemented in ObjectAccess directly: #108
But i just noticed in php how odd it feels and looks to write
if ($renderingMode->isEdit) {
// bla
}
instead of
if ($renderingMode->isEdit()) {
// bla
}
so what are the odds of getting this through?
Is this a simple win?
But i also just found out that code in the mentioned pr from 2015 doesnt exist anymore and is part of the default fluid accessor StandardVariableProvider:
Is there a reason that fluids property access is slightly different than eels?
In fusion/eel i would also like to call
${fooo.isSomething}
which calls the methodisSomething()
to be more descriptive than${fooo.something}
which feels more like a direct getter and will actually use the getter if defined.That was brought to fluid as feature but never implemented in
ObjectAccess
directly: #108Implementing this would make the
RenderingMode
object in Neos better usable in php.To have speaking
is*
access in eel viarenderingMode.isEdit
we cheat our way around this by using public readonly properties:https://github.com/neos/neos-development-collection/blob/e3ff7a4a1f50b2a23c76071536d66506acfa6f8e/Neos.Neos/Classes/Domain/Model/RenderingMode.php#L32-L33
But i just noticed in php how odd it feels and looks to write
instead of
so what are the odds of getting this through?
Is this a simple win?
But i also just found out that code in the mentioned pr from 2015 doesnt exist anymore and is part of the default fluid accessor
StandardVariableProvider
:The text was updated successfully, but these errors were encountered: