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
Currently, it is dependent on the context if true/false/1/0 will be converted to booleans or if the values will remain as-is. This can lead to confusing behavior, for example for a TagBasedViewHelper:
<my:viewhelperdisabled="true" />
This will lead to something like this:
<divdisabled="true"></div>
However, one would expect the following result:
<divdisabled="disabled"></div><!-- or --><divdisabled></div>
However, we can't just convert true or false to boolean in all places because there are cases where you would want the string "true" instead. So we probably need some kind of syntax to decide explicitly, which type should be used.
One possibility is to solve this similarly to frontend frameworks (such as Svelte):
<my:viewhelperdisabled="{true}" />
Same goes for null, which should be treated similarly to true and false.
The text was updated successfully, but these errors were encountered:
Currently, it is dependent on the context if
true
/false
/1
/0
will be converted to booleans or if the values will remain as-is. This can lead to confusing behavior, for example for a TagBasedViewHelper:This will lead to something like this:
However, one would expect the following result:
However, we can't just convert
true
orfalse
to boolean in all places because there are cases where you would want the string"true"
instead. So we probably need some kind of syntax to decide explicitly, which type should be used.One possibility is to solve this similarly to frontend frameworks (such as Svelte):
Same goes for
null
, which should be treated similarly totrue
andfalse
.The text was updated successfully, but these errors were encountered: