Explanation of Ember 3.0 release notes

@miolae wrote:

Hi all! Can anybody explain me one thing from EmberJS 3 description?

In Ember 3.0 reading a computed property without using get will cause an assertion failure in development. This addition of this assertion will help applications correct their currently incorrect usage, and in later 3.x releases allow us to remove the requirement to use get to read a computed property’s value.

I see 2 things here:

1. Adding an assertion failure when reading a computed property without get()
2. Requirement of using get() in this case will be removed in the nearest future

Aren’t these points contradicts each other?

Posts: 2

Participants: 2

Read full topic