Closed cibernox closed 7 years ago
This fails because the bug present in 2.10+.
I'm actually not sure how to fix it, since seems that the component is doing by design something forbidden, here: https://github.com/knownasilya/ember-cli-toggle/blob/master/addon/components/x-toggle/component.js#L34-L39
This usage (modify one value immediatly when received) was discouraged before but since glimmer2 is just forbidden.
Maybe just wrapping it in Ember.run.next
?
Perhaps that could work, although I didn't get exactly why the component wants to immediately set the value on the outside when it's undefined. Shouldn't undefined
be treated as falsey
and just don't do anything?
These are historic changes by @ksnyde, which helped his usecase. Looking back it was probably too specific for the general public. I'd make it simpler and release a 3.0.
:+1: Thanks for this change. Can we get a patch release for this please? Running into that right now with ember-stable (2.11.0).
Released as v3.0.0
cool thx so much 🍻
Ready for merge?