Now that the Angle Bracket Invocation RFC has been merged (馃帀) this issue aims to track landing the functionality proposed there behind the EMBER_GLIMMER_ANGLE_BRACKET_INVOCATION feature flag.
Where possible individual items will cross link to the related section of the RFC.
Ember.Component based components via angle brackets with "capital case" component naming (e.g. <FooBar></FooBar> would find app/components/foo-bar.js). Relevant RFC Section<FooBar @foo={{somethingSpecial}}></FooBar>)....attributes tagName is not ''class attribute should be merged with those in the specified elementhas-block should be false for "self closing" invocations (e.g. <FooBar />)has-block should be true for normal (not self closing) invocations (e.g. <FooBar></FooBar>)<this.foo></this.foo>)<@foo></@foo>)simple-html-tokenizer to support <@foo></@foo> https://github.com/tildeio/simple-html-tokenizer/pull/62 & https://github.com/glimmerjs/glimmer-vm/pull/818didCreateElement on the component's manager for _every_ usage of ...attributes https://github.com/glimmerjs/glimmer-vm/pull/820has-block is false for self closing component invocations (e.g. <FooBar />) https://github.com/glimmerjs/glimmer-vm/pull/819...attributes in the Ember.Component wrapper element https://github.com/glimmerjs/glimmer-vm/pull/823Updated checklist to mark off items from #16686.
Marked has-block support completed (as of https://github.com/emberjs/ember.js/pull/16697) as well as one of the implementation TODO's.
Updated for items completed in https://github.com/emberjs/ember.js/pull/16704.
This is now enabled by default on canary, and barring any additional issues will be included in the 3.4 series of releases.
Most helpful comment
This is now enabled by default on canary, and barring any additional issues will be included in the 3.4 series of releases.