From b9a5d7d08ce06ceb5a5001c45cd31687d215a3f2 Mon Sep 17 00:00:00 2001 From: Jessica Jordan Date: Fri, 7 Dec 2018 18:24:23 +0100 Subject: [PATCH 1/2] blog(embertimes-76): add ember-cli-eslint-writeup --- .../2018-12-07-the-ember-times-issue-76.md | 20 ++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) 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 ec2409b38e..472907d1d6 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 @@ -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 πŸ“, and JSON:API πŸ‡― is getting an update for the holiday season πŸŽ‰πŸŽŠπŸŽˆ! +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 πŸ’¬! --- @@ -42,9 +42,9 @@ Comment and read more about the [RFC on GitHub](https://github.com/emberjs/rfcs/ ## [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)! +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! +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! --- @@ -62,6 +62,20 @@ To learn more about the rest of the features and changes in **JSON:API 1.1** che --- +## [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 the [your thoughts on how to swap Ember CLI ESLint for ESLint know](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/)

This week we'd like to thank @Simran-B, @bhullarg, @jfdnc, @dcyriller, @Turbo87, @jenweber, @MelSumner, @esbanarango, @igorT, @prasannavijayan, @efx, @zachgarwood, @ppcano, @simonihmig, @stefanpenner, @kategengler, @rwjblue, @runspired, @rwwagner90, @thorsteinsson and @jacobq for their contributions to Ember and related repositories! πŸ’–

From 16783ccd5e901297e672b2be59a2927cadfe12d4 Mon Sep 17 00:00:00 2001 From: Amy Lam Date: Fri, 7 Dec 2018 19:15:38 +0100 Subject: [PATCH 2/2] Update source/blog/2018-12-07-the-ember-times-issue-76.md Co-Authored-By: jessica-jordan --- source/blog/2018-12-07-the-ember-times-issue-76.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 472907d1d6..8131cfc403 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 @@ -72,7 +72,7 @@ and your **guidance** as part of the Ember community **is needed**! 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 the [your thoughts on how to swap Ember CLI ESLint for ESLint know](https://github.com/ember-cli/ember-cli/pull/8219) to support the delivery of the best linting solution for the community! +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! ---