This repository has been archived by the owner on Mar 22, 2019. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #3714 from emberjs/blog/embertimes-76
The Ember Times - Issue No. 76
- Loading branch information
Showing
2 changed files
with
111 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,110 @@ | ||
| --- | ||
| title: The Ember Times - Issue No. 76 | ||
| author: Chris Ng, Jessica Jordan, Amy Lam, Alon Bukai | ||
| tags: Recent Posts, Newsletter, Ember.js Times, Ember Times, 2018 | ||
| alias : "blog/2018/12/07-the-ember-times-issue-76.html" | ||
| 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 📝, **fill out** the npm JavaScript Ecosystem Survey 📝, JSON:API 🇯 is getting an update for the holiday season 🎉🎊🎈 and Ember's **linting** future needs your input 💬! | ||
|
|
||
| --- | ||
|
|
||
| ## [Jingle Bells 🔔, Jingle Bells 🔔, ✨ DecEmber 🐹🎄 All the Way!](https://www.emberjs.com/blog/2018/11/29/december-event.html) | ||
|
|
||
| Find one of the issues 🔍 <br> | ||
| In the [Ember Learn project](https://github.com/ember-learn) <br> | ||
| With the [December label in use](https://help-wanted.emberjs.com/learning?label=DecEmber) <br> | ||
| Don't leave the [chat unchecked](https://discordapp.com/channels/480462759797063690/517914929261576212). | ||
|
|
||
| Send in a PR ⬅️<br> | ||
| Make the reviewer smile 🙂 <br> | ||
| What fun [24PullRequests](https://24pullrequests.com/) are <br> | ||
| when the contribution is so [worthwhile](https://www.emberjs.com/blog/2018/11/29/december-event.html)! 🐹 | ||
|
|
||
| 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/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. | ||
|
|
||
| Because tracked properties are just a very thin layer on top of native JavaScript, setting and accessing tracked properties can be done using **standard JavaScript syntax**. With no special syntax, and leveraging existing JavaScript knowledge. | ||
|
|
||
| Comment and read more about the [RFC on GitHub](https://github.com/emberjs/rfcs/pull/410). | ||
|
|
||
| --- | ||
|
|
||
| ## [Ten Minutes to Improve JavaScript 📈](https://www.npmjs.com/2018-javascript-ecosystem-survey) | ||
|
|
||
| Represent Ember in the [2018 JavaScript Ecosystem Survey](https://www.npmjs.com/2018-javascript-ecosystem-survey)! | ||
|
|
||
| Each winter, [npm, Inc.](https://www.npmjs.com/) circulates a survey of software developers and npm users to solicit your feedback and ideas about how to continue supporting the world’s fastest growing developer community and the world’s most popular development language. (Review last year’s results [here](https://www.npmjs.com/npm/state-of-javascript-frameworks-2017-part-1).) Be sure to fill out the survey [here](https://www.npmjs.com/2018-javascript-ecosystem-survey) in order to share what you've been working on and how you plan to use JavaScript in 2019. And spread the word! | ||
|
|
||
| --- | ||
|
|
||
|
|
||
|
|
||
| ## [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). | ||
|
|
||
| --- | ||
|
|
||
| ## [Set the Future Direction of Linting Ember Apps 📝](https://github.com/ember-cli/ember-cli/pull/8219) | ||
|
|
||
| In this [work-in-progress draft for restructuring the linting workflow in Ember applications](https://github.com/ember-cli/ember-cli/pull/8219) the implementation of | ||
| [Ember CLI RFC (Request for Comments) #121](https://github.com/ember-cli/rfcs/pull/121) has begun - | ||
| and your **guidance** as part of the Ember community **is needed**! | ||
|
|
||
| [Based on the RFC's design strategy](https://github.com/sangm/rfcs/blob/master/active/0000-remove-ember-cli-eslint.md#detailed-design) Ember's **linting** story is about to be aligned with best practices used in the general JavaScript ecosystem. | ||
| And there are still decisions to be made: Do you for example expect your linting tests to run | ||
| with `ember build` and `ember serve`? How would you linting integrate best into your CI pipeline? | ||
|
|
||
| Let [your thoughts on how to swap Ember CLI ESLint for ESLint be known](https://github.com/ember-cli/ember-cli/pull/8219) to support the delivery of the best linting solution for the community! | ||
|
|
||
| --- | ||
|
|
||
| ## [Contributors' Corner 👏](https://guides.emberjs.com/release/contributing/repositories/) | ||
|
|
||
| <p>This week we'd like to thank <a href="https://github.com/Simran-B" target="gh-user">@Simran-B</a>, <a href="https://github.com/bhullarg" target="gh-user">@bhullarg</a>, <a href="https://github.com/jfdnc" target="gh-user">@jfdnc</a>, <a href="https://github.com/dcyriller" target="gh-user">@dcyriller</a>, <a href="https://github.com/Turbo87" target="gh-user">@Turbo87</a>, <a href="https://github.com/jenweber" target="gh-user">@jenweber</a>, <a href="https://github.com/MelSumner" target="gh-user">@MelSumner</a>, <a href="https://github.com/esbanarango" target="gh-user">@esbanarango</a>, <a href="https://github.com/igorT" target="gh-user">@igorT</a>, <a href="https://github.com/prasannavijayan" target="gh-user">@prasannavijayan</a>, <a href="https://github.com/efx" target="gh-user">@efx</a>, <a href="https://github.com/zachgarwood" target="gh-user">@zachgarwood</a>, <a href="https://github.com/ppcano" target="gh-user">@ppcano</a>, <a href="https://github.com/simonihmig" target="gh-user">@simonihmig</a>, <a href="https://github.com/stefanpenner" target="gh-user">@stefanpenner</a>, <a href="https://github.com/kategengler" target="gh-user">@kategengler</a>, <a href="https://github.com/rwjblue" target="gh-user">@rwjblue</a>, <a href="https://github.com/runspired" target="gh-user">@runspired</a>, <a href="https://github.com/rwwagner90" target="gh-user">@rwwagner90</a>, <a href="https://github.com/thorsteinsson" target="gh-user">@thorsteinsson</a> and <a href="https://github.com/jacobq" target="gh-user">@jacobq</a> for their contributions to Ember and related repositories! 💖</p> | ||
|
|
||
| --- | ||
|
|
||
| ## [Got a Question? Ask Readers' Questions! 🤓](https://docs.google.com/forms/d/e/1FAIpQLScqu7Lw_9cIkRtAiXKitgkAo4xX_pV1pdCfMJgIr6Py1V-9Og/viewform) | ||
|
|
||
| <div class="blog-row"> | ||
| <img class="float-right small transparent padded" alt="Office Hours Tomster Mascot" title="Readers' Questions" src="/images/tomsters/officehours.png" /> | ||
|
|
||
| <p>Wondering about something related to Ember, Ember Data, Glimmer, or addons in the Ember ecosystem, but don't know where to ask? Readers’ Questions are just for you!</p> | ||
|
|
||
| <p><strong>Submit your own</strong> short and sweet <strong>question</strong> under <a href="https://bit.ly/ask-ember-core" target="rq">bit.ly/ask-ember-core</a>. And don’t worry, there are no silly questions, we appreciate them all - promise! 🤞</p> | ||
|
|
||
| </div> | ||
|
|
||
| --- | ||
|
|
||
| ## [#embertimes](https://emberjs.com/blog/tags/newsletter.html) 📰 | ||
|
|
||
| Want to write for the Ember Times? Have a suggestion for next week's issue? Join us at [#support-ember-times](https://discordapp.com/channels/480462759797063690/485450546887786506) on the [Ember Community Discord](https://discordapp.com/invite/zT3asNS) or ping us [@embertimes](https://twitter.com/embertimes) on Twitter. | ||
|
|
||
| Keep on top of what's been going on in Emberland this week by subscribing to our [e-mail newsletter](https://the-emberjs-times.ongoodbits.com/)! You can also find our posts on the [Ember blog](https://emberjs.com/blog/tags/newsletter.html). | ||
|
|
||
| --- | ||
|
|
||
| That's another wrap! ✨ | ||
|
|
||
| Be kind, | ||
|
|
||
| Chris Ng, Jessica Jordan, Amy Lam, Alon Bukai and the Learning Team |