The Ember.js Times - Issue #42
હેલો Emberistas!

This week we’d like to highlight some soon-to-be-closed RFCs, amazing insights into the internals of your favorite Ember debugging tool and last, but not least, we have a brand new Readers’ Question about best practices regarding data handling in Ember apps for you.
Here’s a wrap up of what has happened these days 🐹: 
I think you’ll like this Ember app that lets you inspect Ember apps…
Did you know there’s this cool Ember app that you can use to debug Ember apps? Sounds familiar? That’s right: Sounds very much like Ember Inspector - your favorite tool for inspecting Routes, Components, Data Models and much more in your app right in your browser. And just recently the folks of Ember Inspector went on a quest to modernize the tool completely. 

Wanna learn more about the inner workings of the Inspector? Check out this screencast walking through the codebase and most importantly, be sure to check out @rwwagner90’s blog post illustrating how the Ember Inspector is becoming even better
Read More
There’s been a lot of debate about how to better improve the Ember community experience. Have a question you’re going to ask on the Ember Slack? Consider writing it up on first to share the knowledge in a searchable forum. Thanks @rwjblue for kicking off the Questions category! 📈
The 3️⃣ Final 2️⃣ Countdown 1️⃣ for AngleBrackets and Copyables in Ember 🐹🚀
This week two RFCs (Request for Comments) entered their Final Comment Period. This means that this is your last chance to check out and comment on the following proposals before they are finalized:

<AngleBracketInvocation />: @chancancode has proposed an RFC to introduce an alternative syntax to invoke components in templates. 
For example, lets say you have a component named super-duper. In the current syntax you would write this component as {{ opening_double_curly() }}super-duper hello=world class=(if true"alon") {{ closing_double_curly() }}. 
In the new syntax this would be: <SuperDuper @hello={{ opening_double_curly() }}world{{ closing_double_curly() }} class={{ opening_double_curly() }}if true“alon"{{ closing_double_curly() }} />.

An RFC by Yehuda Katz from 2015 proposed a similar syntax but was ultimately closed.
The main advantage of the angle bracket syntax is clarity. This syntax will help visually distinguish components from other handlebar constructs, such as control flow and dynamic values. This change is pure syntactic sugar and won’t change any of the underlying component functionality. The syntax proposed is capital letters to distinguish it from both HTML elements and web components. 
A great benefit of this is that we can finally create single word components. Custom <Button> here we come!

Deprecation of Copy & Copyable:  Freeing ember-source from obsolete code has been a recurring theme in the recent RFC landscape. In this regard, the copy method and the Copyable class for creating copies of POJOs and other data objects, might also soon move - as proposed in this RFC - away from Ember. The deprecation wouldn’t be the end to the story though - moving these functionalities into an optional addon would still make these available to any users that rely on them in their apps. 
If you’re curious to learn more about the motivation behind this deprecation, you should check out the proposal here.
The lovely folks at Ember Weekly just sent out the 250th edition (what? yeah, that’s right! 💪) of the celebrated newsletter out this week, marking the 5th birthday of the format! 🎉
Be sure to check out their EmberConf 2018 recap with a full list of videos & slides this week.
An impressed round of 👏 for the folks @EmberWeekly and the original creator @owz for their amazing work on making these five years full of fresh Ember news possible!
We have a special request for everyone in the Ember community this week, no matter if you’re a seasoned Ember expert or someone who just joined us recently.

There are many ways to give back to the community and the best way is to talk about your experience with Ember and how you or your company benefitted from it. Dare to share your thoughts. We have a wonderful panel who can help in reviewing your blog post or even help you come up with one - just pop by the #team-learning Slack channel and let us know your ideas!
If that's not your cup of tea 🍵consider a tweet with a link to your app built with Ember. Make sure to include the #emberjs hashtag. 
This week we have another great Readers’ Question for you that you might have asked yourself when dealing with data handling in your Ember apps: Is it recommended to deal with lots of data fetching in your components? Or is this rather considered an anti-pattern?

Ember Core team member @ef4 is giving a detailed answer to this question this week. You can read his full answer to this question here on the official Ember forum.
Read more
Submit your own short and sweet question under And don’t worry, there are no silly questions, we appreciate them all - promise!  🤞
A shout out to all the amazing contributors who worked on Ember core projects this week: @rwjblue, @williamhaley, @rondale-sc, @Dhaulagiri, @quajo, @brzpegasus, @lukecoy, @toddjordan, @MelSumner, @davewasmer, @runspired, @nummi, @scalvert, @Alonski, @kellyselden, @twokul, @Turbo87, @2hu12, @Gaurav0, @kategengler, @samselikoff and @pzuraq - merci beaucoup! 💖
✨ That's another wrap!  ✨ 

Be kind,
Sivakumar Kailasam, Alon Bukai, Robert Wagner, Amy Lam, Ricardo Mendes, Edward Faulkner, Jessica Jordan 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