This week: Check out the RFC for Improved Ember Registry APIs 🗒️®️, Octane community feedback from FlashRecruit 👏, contributing to OSS with confidence at EmberConf 💪, and meet two developers who write short Ember posts regularly ✏️!
Chris Krycho (@chriskrycho) proposed adding a new, object-based API for all registry APIs; deprecate the current string-based microsyntax registry APIs; and introduce a capabilities property to the resolver to safely support existing resolvers.
The RFC: Improved Ember Registry APIs covers the problems with the microsyntax and the lack of TypeScript support. The RFC recommends adding a new Identifier API which would contain the name, type, and optionally the namespace fields instead of the current microsyntax. For example:
At FlashRecruit, we're building a conversational job marketplace. We've been using Ember Octane since before the official preview--don't tell anyone--to build the new version of our job board and dashboard.
Ember Octane allowed us to quickly prototype an application, move on to production with little tech debt, and feel well supported throughout the process.
We saw a few issues in the preview period, but the community was quick to help us figure out how to move past them. They were mostly fixed by the official release, as well.
We look forward to the enhanced tracking changes coming in RFCs like #577. Honestly, anything beyond this point is just gravy.
We know there are lots of other great examples of Octane being used in the wild. If you’d like to share your experiences, please feel to reach out to the Ember Times team: #support-ember-times on the Ember Community Discord!
With plenty of research on what makes an open-source community successful in facilitating contributions, she will demonstrate how Ember empowers contributors to give back to the project in her talk Why Contributing Seems Scary at this year's EmberConf.
In an exclusive interview with The Ember Times, Anne-Greeth shares with us, who she thinks is qualified to contribute to Ember:
[…] I think everyone can contribute to Ember. It just matters on your opinion of what you think contributing means. So for me contributing goes from helping out at EmberConf, to writing, reading RFCs, and everything in between. And I think as long as you want to. you can always find something for you to contribute to.
What is something that surprises first-time contributors when working on a project like Ember? Anne-Greeth speaks from her previous experience when sharing her OSS journey with others:
From the talk about contributing I gave at EmberFest last year and also one I gave at my work, I noticed that people were surprised how easy it is to contribute. And that contributing doesn’t mean that you necessarily have to fix the problem, but that also identifying a problem is contributing to it. At my company I got the response from somebody who just two hours after my talk already created their first pull request to an open-source repository (which wasn’t Ember), but still he was like “Hey, I did this!” In general, the feedback has been really positive, because my examples are really low-key. People feel really encouraged and inspired, that they can do it, too!
Besides learning how to contribute with confidence, what makes EmberConf a must-visit experience this year? Anne-Greeth talks about what she is looking forward to the most:
I think the people. It sounds really cheesy, but for me, meeting all the people that I met years before, but also meeting new people at different meetups, but also in between talks, is, I think, really cool. And discussing with them things about Ember, but also about culture and about different countries is, I think, one of the best things about EmberConf.