Last month, the members of the organization Ember.js core team Meet face-to-face and remotely, review the development direction of the framework API, solve some architectural design issues, and find the next step. In this article, we will share a summary of the weekend’s discussions and themes.
What will happen in the F2F meeting?
“F2F” stands for face-to-face meetings, where members of the core team get together to solve problems or brainstorm in ways that are difficult to do remotely or in a one-hour meeting. Each core team of Ember meets at least once a year, usually after EmberConf.
All core teams work hard to record their meeting minutes, you can find the agenda and notes of the framework F2F (covering the first day) In the core notes repo.
Read on to get a summary of what is covered.
Octane RFC review
The focus of the F2F agenda is discussion and comment Open RFC, Especially those related to Ember “Octane”. Octane will be Ember’s first Version release, A minor version of the framework was released, along with an updated blueprint for new applications and documentation, with an emphasis on a new programming model. Octane will bring a new and improved developer experience to Ember. This will be a minor (non-destructive change) version of the framework, bringing Ember’s latest and best features to the forefront.
The RFCs discussed include:
- Remove jQuery by default -Removing jQuery from Ember’s default blueprint will affect other packages that your application may use. These packages must now explicitly require it, rather than implicitly exist in jQuery. Most of the feedback and discussion of this RFC focused on the impact of this change on other application dependencies. In addition, some libraries rely on jQuery pre-filters to modify every request to the server (such as adding authorization headers) and request to update the RFC to solve the problem. Read our detailed feedback here.
- Low light component with Render element modifier -The Glimmer component RFC introduces APIs for components that do not contain any DOM-based hooks (for example
didInsertElement). The “Render Element Modifier” RFC aims to bring these APIs back to Ember in a different way. In the discussion, we realized that the API recommended for this narrow situation is very similar to the API you might want to use modifiers as a general tool. An attempt to bridge the gap between this use case and the universal design of callable modifiers was proposed as a goal.
- Tracking attributes
Review website improvement progress
In addition to our API, there are opportunities to update and update more content.As mentioned before Embers times, We are doing important work to improve the structure, look and feel of our public website, emberjs.com. Framework core team members received the latest progress update, and now it is RFC public reviewIn the past year, many parts of the multiple web applications that make up our public site have been refactored to use a central style guide and common UI components, making the upcoming visual refactoring possible.This work is already in Embers style guide.
Significant progress has been made in website accessibility, consistency and better marketing information, but there is still more work to be done! The learning team and the website strike team are working. Please stay tuned for more updates in the new year.
It is safe to say that there is still a lot of work to be done to make up the functionality and documentation of the Octane version!To follow up or provide help, see Octane tracking problem. The new architecture of the public site is an application under development Here.
What’s the next step?
Every time before EmberConfIt is the biggest gathering of Ember developers, and there is always a series of activities. It seems that the first quarter of 2019 may be the most lively! In less than two months, some big plans are underway.Please follow the update in the following ways Embers times, This Ember.js TwitterAnd “watch” ember.js GitHub repository… If you dare.
Hope to see you at EmberConf in March!