Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE ember-htmlbars-component-generation] Disabled by default. #11267

Merged

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented May 24, 2015

A number of issues have been discovered for this feature that make it clear that further consideration is needed before enabling by default.

  • Cannot use angle-bracket invocation in contexts that require specific tags. For example: you cannot use <table><custom-row model=stuff /></table> because in a <table> context like this, you can only use <tr>
  • Need to treat <some-thing /> as blockless and <some-thing></some-thing> as having a block. Both scenarios are considered block invocation today.
  • Cannot use angle-bracket invocation to use components in a subdirectory.
  • Other things...

A more thorough review of what this means for future timing will be coming in a blog post by @wycats shortly...

A number of issues have been discovered for this feature that make it clear
that further consideration is needed before enabling by default.

* Cannot use angle-bracket invocation in contexts that require specific tags.
  For example: you cannot use `<table><custom-row model=stuff></custom-row></table>` because
  in a `<table>` context like this, you can only use `<tr>`
* Cannot use angle-bracket invocation to use components in a subdirectory.
* Other things....
rwjblue added a commit that referenced this pull request May 25, 2015
…on-feature

[FEATURE ember-htmlbars-component-generation] Disabled by default.
@rwjblue rwjblue merged commit 6c4e5ae into emberjs:master May 25, 2015
@rwjblue rwjblue deleted the disable-angle-bracket-invocation-feature branch May 25, 2015 01:18
@wycats
Copy link
Member

wycats commented May 25, 2015

The RFC that led to this disabling is now posted.

Since angle bracket components are our one near-term shot to make useful semantic changes, it seems worth waiting an extra release if we can successfully unify a bunch of concepts that are the source of many papercuts today.

(on top of the issues @rwjblue raised)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants