- Issue created by @attilatilman
- πͺπΈSpain penyaskito Seville π, Spain πͺπΈ, UTC+2 πͺπΊ
Which version of XB are you using? If HEAD, what's the last commit?
- πͺπΈSpain penyaskito Seville π, Spain πͺπΈ, UTC+2 πͺπΊ
Part of π Setting default values does work for boolean props Active was merged since then, which I think is the same issue.
Can you verify with HEAD or using the committed MR as a patch?
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
Actually, no, I'm 100% confident this is identical to the issue that @penyaskito linked in #4.
The only mistake @penyaskito made in #4: π Setting default values does work for boolean props Active had the back-end pieces + a commented out failing e2e test merged β see #3492368-37: Setting default value of `false` does NOT work for boolean props β .
The actual bug remains, and is a pure client-side problem.
Transfering credit there.