From 4f90ef1645162e3738296ddb15807e2b47f685b8 Mon Sep 17 00:00:00 2001 From: Chris Ng Date: Thu, 6 Sep 2018 15:34:52 -0400 Subject: [PATCH 1/2] blog(embertimes#63): 2 RFCs for Computed Props --- source/blog/2018-09-07-the-ember-times-issue-63.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/source/blog/2018-09-07-the-ember-times-issue-63.md b/source/blog/2018-09-07-the-ember-times-issue-63.md index 237399617f..799705247e 100644 --- a/source/blog/2018-09-07-the-ember-times-issue-63.md +++ b/source/blog/2018-09-07-the-ember-times-issue-63.md @@ -52,8 +52,15 @@ The time has come: The **Ember Community is starting its big move over to [Disco --- -## [SECTION TITLE](#section-url) +## New Computed Property RFCs Deprecating [volatile()](https://github.com/emberjs/rfcs/pull/370) and [readOnly()](https://github.com/emberjs/rfcs/pull/369) 2️⃣ + +[Chris Garrett](https://github.com/pzuraq) proposed two new RFCs on [computed properties](https://guides.emberjs.com/release/object-model/computed-properties/). Both RFCs are centered around deprecating functions to adjust the defaults to what the common use cases developers face and to better align with native class syntax. + +The RFC to [deprecate computed overridability and readOnly()](https://github.com/emberjs/rfcs/pull/369) seeks to align computed properties to the native class syntax getters and setters by deprecating computed overridability (colloquially known as "clobbering") and make computeds read-only by default turning this uncommonly used feature to an opt-in using the overridable API. + +Similarly, the RFC to [deprecate computed().volatile()](https://github.com/emberjs/rfcs/pull/370) was proposed to favour native accessors rather than relying on the volatile API to provide that functionality. This is to align what users expect versus what the framework does, which is almost exactly what the native accessors do except it swallows notification changes. +Join the conversation at the respective pull requests for [volatile()](https://github.com/emberjs/rfcs/pull/370) and [readOnly()](https://github.com/emberjs/rfcs/pull/369)! --- From 0ed8b71f302e08dc5d27f0593785e8bb207bf4eb Mon Sep 17 00:00:00 2001 From: Chris Ng Date: Thu, 6 Sep 2018 18:18:26 -0400 Subject: [PATCH 2/2] blog(embertimes#63): Link for native class syntax --- source/blog/2018-09-07-the-ember-times-issue-63.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/blog/2018-09-07-the-ember-times-issue-63.md b/source/blog/2018-09-07-the-ember-times-issue-63.md index 799705247e..28f14f4ffd 100644 --- a/source/blog/2018-09-07-the-ember-times-issue-63.md +++ b/source/blog/2018-09-07-the-ember-times-issue-63.md @@ -54,7 +54,7 @@ The time has come: The **Ember Community is starting its big move over to [Disco ## New Computed Property RFCs Deprecating [volatile()](https://github.com/emberjs/rfcs/pull/370) and [readOnly()](https://github.com/emberjs/rfcs/pull/369) 2️⃣ -[Chris Garrett](https://github.com/pzuraq) proposed two new RFCs on [computed properties](https://guides.emberjs.com/release/object-model/computed-properties/). Both RFCs are centered around deprecating functions to adjust the defaults to what the common use cases developers face and to better align with native class syntax. +[Chris Garrett](https://github.com/pzuraq) proposed two new RFCs on [computed properties](https://guides.emberjs.com/release/object-model/computed-properties/). Both RFCs are centered around deprecating functions to adjust the defaults to what the common use cases developers face and to better align with [native class syntax](https://github.com/emberjs/rfcs/pull/338). The RFC to [deprecate computed overridability and readOnly()](https://github.com/emberjs/rfcs/pull/369) seeks to align computed properties to the native class syntax getters and setters by deprecating computed overridability (colloquially known as "clobbering") and make computeds read-only by default turning this uncommonly used feature to an opt-in using the overridable API.