Ember Times-Issue 63


Sholem-aleykhem Emberistas! 🐹

Be sure to join the new Ember community chat on Discord💬! This week, you can take a look at Ember Data’s Meta Quest 🔜, some fresh 🍎 RFCs, ideas on fostering the Ember community💛, and special thanks to @mmun 🎉.


The time has come: The Ember community is beginning to Discord. As in The original and recently accepted RFC for the migration (for comments) You can now to chat with and yours Embers friends 🐹👭👬👫 Ember Discord servers from all over the world.This brings-among other benefits-has the following advantages Unlimited message history.

Check out the new community chat now, Must Set up your profile As mentioned in #setup-profile Channel and join #discord-server-admin Visit your favorite discussions💬.


The Ember Data team is seeking community help to release RecordData stably!You can read more about RecordData RFC #293. RecordData encodes the internal structure of Ember Data, enabling plug-in developers to access the required APIs more confidently and stably.

Community Action Project:

  • once 3.5.0-beta.2 Released, please configure your application/plug-in to test against this version!
  • Report errors encountered, and help classify/copy as much as possible.
  • Help refactor existing plug-ins to take advantage of RecordData instead of private APIs that may be deleted.For a good list of getting started, see Ember Data’s External partner testing.

@davewasmer Have written an RFC introduction versionThe idea is that every few years Ember will release a new version of Ember, bundling cumulative incremental improvements into a cohesive package.

The benefit of this is that it gives the Ember community the opportunity to update our documentation and marketing to reflect the improvements we have made since the last version. According to the RFC, the correct time to declare the new version is:

  • A set of important and coherent new features and APIs have been registered on the stable channel.
  • The error messages of these new features and the ergonomics of the developers have been completely perfected.
  • Tools (Ember Inspector, blueprints, codemods, etc.) have been updated to use these new features.
  • The API documentation, guides, tutorials, and sample code have been updated to include new features.

make sure Read the entire RFC with Leave your thoughts.


New calculated property RFC deprecation Volatile () with Read only() 2️⃣

@pzuraq Two new RFCs are proposed Calculated attributesBoth RFCs are centered on deprecated functions to adjust the default values ​​to common use cases faced by developers and better integrate with Native class syntax.

RFC to Deprecated computing coverage and readOnly() Trying to align calculated properties with native class syntax getters and setters by deprecating calculation coverage (commonly known as “clobbering”), and make calculations read-only by default, and use overridable APIs to convert this uncommon function into opt-in .

Similarly, the RFC to Deprecated calculation(). Volatile () It is proposed to support native accessors instead of relying on volatile API to provide this function. This is to align what users expect the property to do when the value changes with what the framework does (including notification changes).

Join the conversation in the corresponding pull request Volatile () with Read only()!


“Ember is a big tent” was recently used @tomdale When the Ember developer asked if he Ember is still a popular community.

With this topic in mind, Tom Dale shared the following thoughts:

  • Encourage everyone to share their views on the framework and the path it takes, even if they disagree with the core team or the entire community, if people think they must remain silent, the community will fail.

  • It is dangerous when the developer community creates a spell that they repeat endlessly, because the original context surrounding why may be lost, and then people may tend to assume the spell without knowing its original purpose and forget about it. The underlying assumptions may change.

  • There is no “right way” to build an Ember application, and no one other than the developer in question has a better understanding of the specific tools needed to make the team more efficient and the project successful.

  • If we don’t follow other existing frameworks and the broader JavaScript ecosystem to learn from their ideas, we as Ember developers will hurt ourselves.

  • Before taking defensive measures, we should empathize, understand the setbacks experienced by others, and provide help and constructive criticism.

The big tent analogy used means that Ember is an open community, and different individuals with different ideas and opinions about the framework are welcome and the correct way to use it in our own projects.

Although Ember comes with a set of default values ​​and guidelines, it is unrealistic to think that these same default values ​​apply to every project in every situation.

To quote Tom’s final reasoning: “Let’s make sure we are cultivating a community that does not suppress ideas.”


This week, we would like to take a moment to express our heartfelt thanks to a very dedicated contributor:
Martin Muñoz (@mmun) Not only has he been an active contributor to Ember for many years, but he is also a member of Ember’s core team Embers joined Alumni this week.

since His first pull request to the ember.js repository -Submit bug fixes for the former failed test ember-views package-Martin has been actively contributing to Ember and related projects.in Martin joined the Ember core team in June 2015 And is committed to helping Ember become our framework and community today. We thank him for all his hard work on this project, as well as all the understanding, support and sympathy he shows to anyone in the community every day. In this regard, we want to say again: Thank you, Martin!


This week we want to thank @btecu, @赛博诺克斯, @rwjblue, @道拉吉里, @Peter-v, @TeamGame_Shhhhhhhhhhhhhhh, @jessica-Jordan, @andrewpye, @blimmer, @阿隆斯基, @kturney, @jrjohnson, @happycollision, @samselikoff, @nlfurniss, @vitch, @rwwagner90, @CodingItWrong, @twokul, @astronomersiva, @凯特根格勒, @22s, @veelenga, @tylerturdenpants, Mansona, @sivakumar-kailasam with @anotheredward Thanks for their contributions to Ember and related repositories 💖!


Want to know about Ember, Ember Data, Glimmer, or plugins in the Ember ecosystem, but don’t know where to consult? Readers’ questions are only answered for you!

Submit your own Short and sweet problem under bit.ly/ask-ember-coreDon’t worry, there are no stupid questions, we thank them-guaranteed! 🤞


Want to write for Ember Times? Any suggestions for next week’s problem?Join us at #support-ember-times Ember community discord Or ping us @embertimes On Twitter.


That is another package! ✨

Be kind,

Jessica Jordan, Miguel Braga Gomes, Chris Ng, Kenneth Larsen, Amy Lam, Ryan Mark and the learning team



Leave a Reply

Your email address will not be published. Required fields are marked *