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
The else path of an inline if helper used to return undefined, but starting with v3.25 it now returns null, which can be problematic in components that check for the existence of an argument via this.args.foo !== undefined.
🔬 Minimal Reproduction
<SomeComponent @foo={{ifthis.bar"baz"}} />
😕 Actual Behavior
When bar is truthy then foo will be "bar", if not, then it will be null.
🤔 Expected Behavior
When bar is truthy then foo will be "bar", if not, then it will be undefined.
🌍 Environment
Ember: 3.25.1
The text was updated successfully, but these errors were encountered:
in our case about 900 tests are failing in the test suite due to this unintentional change 😅
I guess usually I would just do if (this.arg.foo) {...}, but since @foo can be a number in our case and that number is allowed to be zero we went for the this.arg.foo !== undefined check.
🐞 Describe the Bug
The
else
path of an inlineif
helper used to returnundefined
, but starting with v3.25 it now returnsnull
, which can be problematic in components that check for the existence of an argument viathis.args.foo !== undefined
.🔬 Minimal Reproduction
😕 Actual Behavior
When
bar
is truthy thenfoo
will be"bar"
, if not, then it will benull
.🤔 Expected Behavior
When
bar
is truthy thenfoo
will be"bar"
, if not, then it will beundefined
.🌍 Environment
The text was updated successfully, but these errors were encountered: