Final month, members of the Ember.js Core Group met in-person and remotely to overview the route that the framework API is headed, work via some architectural design questions, and determine subsequent steps. On this article, we’ll share a abstract of the discussions and themes of the weekend.
What occurs in a F2F assembly?
“F2F” stands for face-to-face, a gathering the place members of a core workforce get collectively to work on issues or brainstorm in a means that’s troublesome to do remotely or in one-hour conferences. Every of the core groups of Ember meets not less than yearly, usually proper after EmberConf.
All core groups make an effort to retains notes of their conferences, and yow will discover the agenda and notes (protecting day one) for the framework F2F within the core notes repo.
Learn on for a abstract of what was lined.
Octane RFC overview
The F2F agenda targeted on discussing and commenting on open RFCs, particularly these associated to Ember “Octane”. Octane shall be Ember’s first version launch, a minor model launch of the framework accompanied by up to date blueprints for brand spanking new apps and documentation that focuses on new programming fashions. Octane will convey a brand new and improved developer expertise to Ember. It is going to be a minor (non-breaking change) launch of the framework that brings Ember’s latest and greatest options to the forefront.
Among the many RFCs mentioned have been:
- Template Imports – The Module Unification Packages RFC launched a technique to import parts from an addon right into a template. There may be quite a lot of curiosity in unifying any import design with the semantics and syntax of JavaScript itself, and this was debated extensively. Preserve your eyes peeled for an RFC discussing concrete API proposals!
- Take away jQuery by default – Dropping jQuery from Ember’s default blueprint impacts different packages your app could use. As an alternative of jQuery being implicitly current, these packages should now explicitly require it. A big a part of the suggestions and dialogue of this RFC was targeted on the impacts this transformation has on different app dependencies. Moreover some libraries are dependent upon jQuery prefilters to switch each request to a server (for instance so as to add an authorization header), and updates to the RFC have been requested to handle that. Learn our detailed suggestions right here.
- Glimmer Parts and Render Component Modifiers – The Glimmer Parts RFC introduces an API for parts that doesn’t embrace any DOM-based hooks (for instance
didInsertElement). The “Render Component Modifiers” RFC is meant to convey these APIs again into Ember with a special strategy. Within the dialogue we realized the APIs being steered for this slender case are extraordinarily much like the APIs you may want for modifiers as a basic instrument. Making an attempt to bridge the hole between this use-case and a generalized design for invokable modifiers was introduced up as a aim. - Editions
- Tracked Properties
- Decorators
One of many framework’s essential strengths is that Ember apps have unusual longevity in comparison with many different apps within the JavaScript ecosystem. We imagine it’s essential that these new options all work effectively as a complete unit, when it comes to present consumer adoption, new learner expertise, and technical efficiency.
To be taught extra about Octane and the way these RFCs work to help it, see the 2018 Roadmap RFC by Tom Dale, which introduces Octane, and the Editions RFC by Dave Wasmer.
Overview of web site enchancment progress
There is a chance to refresh and renew greater than our APIs. As beforehand described in The Ember Instances, vital work is underway to enhance the structure, look, and really feel of our public web site, emberjs.com. Framework core workforce members obtained an replace on the most recent progress, which is now an RFC open to public overview. Over the previous 12 months, many items of the a number of internet apps that make up our public web site have been refactored to make use of a central model information and customary UI parts, making the upcoming visible refactor attainable. This work has been achieved in ember-styleguide.
There was main progress in accessibility, consistency, and higher advertising messaging of the positioning, however there’s nonetheless extra work to do! The Studying Group and the Web site Strike workforce are on the job. Keep tuned for extra updates within the new 12 months.
Motion objects
It’s secure to say that there’s quite a lot of work to do for the options and documentation that make up the Octane version! To observe alongside or assist out, see the Octane Monitoring Concern. The brand new structure for the general public web site is a piece in progress app discovered right here.
What’s subsequent?
Earlier than each EmberConf, the most important gathering of Ember devs, there’s all the time a flurry of exercise. It looks like the primary quarter of 2019 may be the liveliest one but! There are lower than two months to go, and a few huge plans underway. Keep tuned for updates through The Ember Instances, the Ember.js Twitter, and “watch” the ember.js GitHub repository… in case you dare.
Hope to see you in March at EmberConf!
