Past issues Subscribe

Dec 22 2017

The Ember.js Times - Issue #26

🎄 The Ember.js Times 🎄 Issue #26 
Nnọọ Emberistas!

The last week before the holidays 🎄🎅🤶❄️✨ is full with final comments to major RFCs and lots of great contributions to the Ember ecosystem. Here are the highlights of what happened in Ember, Ember Data and Ember CLI this week:
Several deprecations have been removed this week, including those for keyForAttribute, shouldSerializeHasMany, several data transforms and Ember.Date.parse, non-primitive defaultValues of DS.attr and obsolete instance initializers. Finally, an ember-try scenario for the project has been fixed,  tests have been cleaned up and the documentation has been updated, too (1, 2, 3).

Also in the effort to bring testing blueprints according to the simplified QUnit testing API to future Ember apps, the blueprints for both data Models  and transforms landed this week.

A warm thank you goes to the Ember Data enthusiasts @efx, @alexander-alvarez, @bmac and @toddjordan for their work this week. đź’•
First, a new RFC (Request for Comments) has been opened this week proposing the introduction of the let template helper. It will allow you to create bindings for dedicated blocks in your template. You can read more about the motivation behind the new helper in the RFC description.
Second, here comes a sweet reminder for you to review four of recently opened RFCs which entered their final comment period this week: The proposals for template-only components, for a removing the wrapper around the application’s root element, the RFC for a Named Args Syntax and also the the proposal for bringing ES5 getters to Ember are waiting for latest suggestions from the community. 

Lots of enthusiastic contributors worked on unifying the patterns for the internal test suites; the updated tests for @ember/debug, @ember/utils and the container module landed this week. If you feel curious about updating some of these internal tests yourself, feel free to check out the related issue and claim one of the sub tasks.

The testing blueprint for bringing the renewed Acceptance Testing API to Ember apps has landed this week. If you’d like to try out these new blue prints for your acceptance tests today, don’t miss this useful polyfill to get you started.

Also this week’s efforts went into improving the code quality of the project, enforcing and widening the application of ES & TS Linting rules (1, 2). A regression for the test runner has been fixed and with the dropped support for IE9 in Ember 3.0, related feature detection checks and fallbacks for tests were removed. 
And finally, also lots of refactor work went into Ember this week (3, 4, 5, 6, 7, 8, 9, 10).

Many thanks to @chancancode, @cibernox, @locks, @bekzod, @ef4, @t-sauer and @rwjblue for their contributions to Ember this week. 🎉
The introduction of the module-unification-app blueprint marks the beginning of several changes bringing the unified project layout to applications. Using the new MODULE_UNIFICATION flag, applications are now able to be scaffolded according to the new structure when a new project is created. 

Furthermore an update to the test-helper module now ensures that the application’s full set of configuration properties is reflected correctly in the testing environment.

Finally, the .npmignore file now shows in its correct alphabetical order (1, 2).

We’d like to thank @GavinJoyce, @kellyselden and @rwjblue for their work on Ember CLI this week. 💖
✨ We wish you happy holidays with your ♥️ ones and see you again next week ✨

Be kind,
Jessica Jordan, Jen Weber and the Learning Team
Until the next issue, happy Embering :)
The Ember.js Learning Team · 812 SW Washington St, Ste 1000 · Portland OR 97205 · USA
Unsubscribe | View in browser

Previous Issues

Load More