diff --git a/source/blog/2018-12-07-the-ember-times-issue-76.md b/source/blog/2018-12-07-the-ember-times-issue-76.md index 62e0e5a245..d766d238f6 100644 --- a/source/blog/2018-12-07-the-ember-times-issue-76.md +++ b/source/blog/2018-12-07-the-ember-times-issue-76.md @@ -1,6 +1,6 @@ --- title: The Ember Times - Issue No. 76 -author: Chris Ng, Jessica Jordan, Amy Lam, the crowd +author: Chris Ng, Jessica Jordan, Amy Lam, Alon Bukai the crowd tags: Recent Posts, Newsletter, Ember.js Times, Ember Times, 2018 alias : "blog/2018/12/07-the-ember-times-issue-76.html" responsive: true @@ -8,7 +8,7 @@ responsive: true Ξ΅te sΞ΅n Emberistas? 🐹 -Join us with your **contributions** for **DecEmber** πŸΉπŸŽ„, read more about using `@tracked` in the new RFC πŸ‘£, **fill out** the npm JavaScript Ecosystem Survey πŸ“... +Join us with your **contributions** for **DecEmber** πŸΉπŸŽ„, read more about using `@tracked` in the new RFC πŸ‘£, **fill out** the npm JavaScript Ecosystem Survey πŸ“ and JSON:API πŸ‡― is getting an update for the holiday season πŸŽ‰πŸŽŠπŸŽˆ! --- @@ -30,7 +30,7 @@ Jingle bells, jingle bells, **DecEmber** all the way! πŸΉπŸŽ„ ## [Tracked Properties RFC Is Up for Review! πŸ‘£](https://github.com/emberjs/rfcs/pull/410) -The [Tracked Properties RFC](https://github.com/tomdale/rfcs/blob/5710d6e6fdc4ae283af7259800beb18aecb95c0d/text/0000-tracked-properties.md) introduces a simpler and more ergonomic system for tracking state change in Ember applications. +The [Tracked Properties RFC](https://github.com/emberjs/rfcs/blob/be351b059f08ac0fe709bc7697860d5064717a7f/text/0000-tracked-properties.md) introduces a simpler and more ergonomic system for tracking state change in Ember applications. Developers can identify if a property or a getter should be _autotracked_ by adding a `@tracked` decorator to it. This allows that value to have its dependencies automatically detected as it is used. @@ -50,8 +50,15 @@ Each winter, [npm, Inc.](https://www.npmjs.com/) circulates a survey of software -## [SECTION TITLE](#section-url) +## [JSON:API Update 1.1 πŸ‡―](https://twitter.com/jsonapi/status/1069593631365959680) + +**JSON:API 1.1 RC1** is released! πŸŽ‰πŸŽŠπŸŽˆ The spec will hopefully be finalized by January 31 which is very exciting! If you use JSON:API and are able to, try out the upcoming version and give some feedback. + +One notable feature is the addition of **"profiles"** which allow specifying addition semantics on top of the current spec. This could allow specifying things like filtering, pagination and more. Check out [profiles here](https://jsonapi.org/extensions/). + +Another noteworthy change is the official recommendation to use camelCase for resource fields. This standardization will allow composing and parsing **JSON:API** with JavaScript and other languages. Check it out [here](https://jsonapi.org/recommendations/#naming). +To learn more about the rest of the features and changes in **JSON:API 1.1** check out the [Update History](https://jsonapi.org/#update-history). --- @@ -113,4 +120,4 @@ That's another wrap! ✨ Be kind, -Chris Ng, Jessica Jordan, Amy Lam the crowd and the Learning Team +Chris Ng, Jessica Jordan, Amy Lam, Alon Bukai the crowd and the Learning Team