We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Iterable text fields are displayed incorrectly in flex-object list view: e.g.: ["Value1","Value2"]
["Value1","Value2"]
Iterable text fields in flex-object list view are rendered from template [templates/forms/fields/text/edit_list.html.twig]
There are bug in statement introduced in commit {% set value = iterable ? value|join(', ') : value|string %}
{% set value = iterable ? value|join(', ') : value|string %}
As per my understanding value is iterable ? must be used instead of iterable ? because there are no iterable variable in twig context
value is iterable ?
iterable ?
iterable
To make it work, I am using following statement: {% set value = (value is iterable) ? value|map(item=>item|string)|join(', ') : value|string %}
{% set value = (value is iterable) ? value|map(item=>item|string)|join(', ') : value|string %}
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Iterable text fields are displayed incorrectly in flex-object list view:
e.g.:
["Value1","Value2"]Iterable text fields in flex-object list view are rendered from template
[templates/forms/fields/text/edit_list.html.twig]
There are bug in statement introduced in commit
{% set value = iterable ? value|join(', ') : value|string %}As per my understanding
value is iterable ?must be used instead ofiterable ?because there are noiterablevariable in twig contextTo make it work, I am using following statement:
{% set value = (value is iterable) ? value|map(item=>item|string)|join(', ') : value|string %}The text was updated successfully, but these errors were encountered: