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

Cannot use 'error' as a component name #11214

Closed
amk221 opened this issue May 19, 2015 · 4 comments
Closed

Cannot use 'error' as a component name #11214

amk221 opened this issue May 19, 2015 · 4 comments

Comments

@amk221
Copy link
Contributor

amk221 commented May 19, 2015

I have a component like this: {{ui-form/field}}
its template contains: {{error}} (error is a string)

I get the error ""Assertion Failed: You canot use 'error' as a component name. Component names must contain a hyphen."

It works in Ember 1.12 beta 3, but not 1.13. (I'm using ember-cli 0.2.5)

I tried to make a fiddle, but was unable to re-produce the error so I think it must be to do with the ember cli resolver?

My work around for the time being is to do this: {{if error error}}

@rwjblue
Copy link
Member

rwjblue commented May 19, 2015

I do not think this is related to the ember-cli resolver directly, and I am having trouble replicating the error in similar circumstances. Simple JSBin attempt here: http://emberjs.jsbin.com/rwjblue/516/edit.

The assertion is triggered from here (not the resolver) so it should be the same in JSBin if we can figure out the scenario that triggers it...

@mixonic
Copy link
Sponsor Member

mixonic commented May 19, 2015

I'm also seeing this in https://github.com/aptible/dashboard.aptible.com/blob/master/tests/acceptance/claim-test.js#L134-L145. Trying to create a reproducible case.

I've also noted that we are looking up many non-dashed things in the container:

If I add an {{#if}} to the template, we also look that up. Seems incorrect that these are requested from the container at all.

@devinus
Copy link
Member

devinus commented May 19, 2015

Am getting this as well.

@rwjblue
Copy link
Member

rwjblue commented May 20, 2015

Fixed by #11222.

@rwjblue rwjblue closed this as completed May 20, 2015
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

No branches or pull requests

4 participants