-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
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
Allow passing null/undefined literals subexpressions #990
Comments
Not just subexpressions. They would need to fit anywhere an Expression can go. In theory the HTMLBars parser could deal with this (by substituting any PathExpression whose |
Thank you!! :) |
BTW your patch doesn't support {{null}} and {{undefined}} so it diverges from how boolean/number/etc are treated. I don't really care that much though. Sorry to be a pain... |
Thanks. |
Released in 3.0.2 |
I originally filed this on the Ember.JS tracker but was directed here, instead.
It would be really great if subexpressions could handle
null
andundefined
literals. It doesn't appear to work that way currently. I have an EmberJS JSBin that shows the issue I'm talking about.The text was updated successfully, but these errors were encountered: