Simon André
Simon André
The failing test surprises me a bit ... @WebMamba any idea ? I feel we may have exposed more than we wanted
Would you like to work on this feature ?
With the incoming [``](https://github.com/symfony/ux/pull/2303) and [``](https://github.com/symfony/ux/pull/2302), do you think we still need this features ?
Looks good to me! Could you check the type of values and throw if not expected (a non-stringable object) ?
After some thinking, why don't we rename the `custom($action)` method in `action($name, .... ... ... .. )` ?
Let's use action in both then (sorry for the late comment)
@DRaichev we will probably release a 2.22 in the coming weeks, you can use it with the "2.x-dev" in the meanwhile! Thanks for this PR 😄
Thank you for such a kind message—it really means a lot!
@wouterj I indeed missed that discussion, thanks for the link! 😃 I am still not entirely convinced, and will share my reasoning. **But** this is **all but an important topic**,...
In 3.21.x, using parenthesis seems to provide the behaviour you expect. ```twig {% set something = [ ...(true ? ['a'] : ['b']) ] %} ``` But indeed the same expression...