It’d be awesome if we had Babel 7 in Ember CLI around the same time it goes stable, to be able to do optional property chaining :)
-
-
-
Optional chaining is not even stage 2 yet, with lots of TC39 skepticism. I'd be careful with that one.
-
Oh. I didn't know that, thanks for the warning! What are the most common patterns for avoiding deep chaining?
End of conversation
New conversation -
-
-
What would be nice is automatic dependency tracking on computed properties, so every get automatically gets added as a dependency during compilation.
-
It's very unlikely/impossible. What if I did `this.get(someVariable)`, i.e not use string literals? You can make it even more complicated and assume that this value isn't known until runtime.
-
Yes, but it could be based on best effort. Don’t make it mandatory, though.
-
I agree that the current API could be improved, but I think that would introduce more complications than advantages. Besides, maybe not everything that you .get is something you want to observe?
-
We tried out automatic dependency tracking in Glimmer.js. It works reliably but is a bit of a performance regression. We have to work that out before landing something like it in Ember because it's such a hot path.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.