RFC #0287 - Tracking for Promote {{-in-element}} to public API

[kategengler]

RFC #0287 - Tracking for Promote {{-in-element}} to public API

Champion: @rwjblue

---

Expand for Instructions

All teams need to consider a merged RFC to plan any required work. Each team should comment on or edit this with links to issues for the work (or a note to the effect of "No work required").

See the README for more information
See #3 for an example

Under each team, for each repo requiring work for the RFC under that team:
### [repo name](repo url)

- [ ] (issue or pr) description, (issue or pr) link

Remove Repos that do not apply, conversely, there will probably be other repos that need work and should be added.

Ember.js Team:

glimmer-vm

• implement semantic change ([FEATURE | BREAKING] Change semantics of in-element to match emberjs/rfcs#287 glimmerjs/glimmer-vm#918)

ember.js

• upgrade glimmer-vm dependency
• document API
• release

Ember CLI Team:

N/A

Ember Data Team:

N/A

Learning Team:

ember.js

• Add documentation for new built-in helper {{in-lement}} to the API Docs: Document {{in-element}} helper ember.js#17947

guides-source

• Add a section on the usage of {{in-element}} to the Guides, incl. at least one descriptive example: Add documentation for {{in-element}} helper ember-learn/guides-source#751

addon ecosystem

• Reach out to maintainers of ember-wormwhole or ember-elsewhere to point users to new framework-provided helper in their docs

Steering Committee:

N/A

[simonihmig]

For the record: https://github.com/kaliber5/ember-in-element-polyfill has been updated to include the semantic change of the RFC as of v0.2.0, and should work as a polyfill going back to Ember 2.12!

[mansona]

I've done a bit of digging and it looks like the change was made to glimmer-vm in glimmerjs/glimmer-vm@22d1ea9 which was then released in [email protected] 🤔

As the glimmer-vm was updated past v0.40.0 in emberjs/ember.js@ade8188 does that mean that the public {{in-element}} API is available from Ember v3.18?

[simonihmig]

@mansona my understanding is that though GlimmerVM has indeed been updated, and features all what is necessary to expose a public in-element, this has not been done yet on the side of Ember. See:

• [BUGFIX beta] Avoid breaking {{-in-element}} usage ember.js#18727
• https://github.com/emberjs/ember.js/blob/master/packages/ember-template-compiler/lib/plugins/transform-in-element.ts#L11-L44

Though I am also curious what is preventing us from doing the necessary updates on Ember's side to make in-element public? /cc @rwjblue @chancancode

If it's "just" time to work on it, that I could try it...

[simonihmig]

A few points can be checked off here:

• GlimmerVM has ben update a while ago
• support in Ember has just been unlocked ([FEATURE] Add support for public in-element ember.js#18867)
• API docs where a part of that

[locks]

It has been enabled in canary via emberjs/ember.js#18927.

[sandstrom]

Regarding the "addon ecosystem" todo above I've submitted two PRs. Maybe that's enough to tick that box here? Still up to them to decide, but at least we've pinged them now.

• Mention in-element yapplabs/ember-wormhole#122
• Mention in-element ef4/ember-elsewhere#44