{"action":"created","issue":{"url":"https://api.github.com/repos/emberjs/ember.js/issues/12590","labels_url":"https://api.github.com/repos/emberjs/ember.js/issues/12590/labels{/name}","comments_url":"https://api.github.com/repos/emberjs/ember.js/issues/12590/comments","events_url":"https://api.github.com/repos/emberjs/ember.js/issues/12590/events","html_url":"https://github.com/emberjs/ember.js/issues/12590","id":116469104,"number":12590,"title":"Angle components can't be rendered using the {{component}} helper","user":{"login":"renato-zannon","id":486508,"avatar_url":"https://avatars.githubusercontent.com/u/486508?v=3","gravatar_id":"","url":"https://api.github.com/users/renato-zannon","html_url":"https://github.com/renato-zannon","followers_url":"https://api.github.com/users/renato-zannon/followers","following_url":"https://api.github.com/users/renato-zannon/following{/other_user}","gists_url":"https://api.github.com/users/renato-zannon/gists{/gist_id}","starred_url":"https://api.github.com/users/renato-zannon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/renato-zannon/subscriptions","organizations_url":"https://api.github.com/users/renato-zannon/orgs","repos_url":"https://api.github.com/users/renato-zannon/repos","events_url":"https://api.github.com/users/renato-zannon/events{/privacy}","received_events_url":"https://api.github.com/users/renato-zannon/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-11-12T02:53:45Z","updated_at":"2015-11-13T23:32:22Z","closed_at":null,"body":"I'm experimenting with porting some components to angle bracket style in canary, and ended up stumbling on this. When I use `{{component \"my-angle-component\"}}` Ember errors out with: \r\n```\r\nAssertion Failed: You cannot invoke the 'my-angle-component' component with curly braces, because it's a subclass of GlimmerComponent. Please invoke it as '<my-angle-component>' instead.\r\n```\r\nwhich suggests that the `{{component}}` code path hasn't been prepared for angle components yet.\r\n\r\nSo, my questions are:\r\n\r\n1. Is this supposed to \"just work\", as if I had written `<my-angle-component>` in the first place? Or is there some higher-level definition pending to decide what the behavior should be?\r\n2. If the expected behavior here is the \"obvious\" one, is this something that someone new to the Ember codebase (though very familiar with Ember and JS in general) could work on? Or should I just go back to using curly components and wait? :)\r\n\r\n**Update**: It seems to work alright if I use `{{component \"<my-angle-component>\"}}` (with requires some `concat`ing, in my case). Not sure if this is intentional though, I wasn't able to find any explicit tests for this case"},"comment":{"url":"https://api.github.com/repos/emberjs/ember.js/issues/comments/156590125","html_url":"https://github.com/emberjs/ember.js/issues/12590#issuecomment-156590125","issue_url":"https://api.github.com/repos/emberjs/ember.js/issues/12590","id":156590125,"user":{"login":"Serabe","id":36221,"avatar_url":"https://avatars.githubusercontent.com/u/36221?v=3","gravatar_id":"","url":"https://api.github.com/users/Serabe","html_url":"https://github.com/Serabe","followers_url":"https://api.github.com/users/Serabe/followers","following_url":"https://api.github.com/users/Serabe/following{/other_user}","gists_url":"https://api.github.com/users/Serabe/gists{/gist_id}","starred_url":"https://api.github.com/users/Serabe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Serabe/subscriptions","organizations_url":"https://api.github.com/users/Serabe/orgs","repos_url":"https://api.github.com/users/Serabe/repos","events_url":"https://api.github.com/users/Serabe/events{/privacy}","received_events_url":"https://api.github.com/users/Serabe/received_events","type":"User","site_admin":false},"created_at":"2015-11-13T23:32:22Z","updated_at":"2015-11-13T23:32:22Z","body":"Sorry for the delay. Tomorrow I'll be catching a flight to India, I'll b\nthere for two weeks and quite likely I'll have time to address this.\n\nSo far, I like @rwjblue's idea of marking the automut and \"unboxing\" it.\nOn Fri, 13 Nov 2015 at 20:49, Robert Jackson <notifications@github.com>\nwrote:\n\n> I believe there was consensus that a GlimmerComponent could be used, and\n> that auto-mut would not apply (normal glimmer component semantics).\n>\n> A few notes:\n>\n>    - Auto-mut happens as a compilation step, where we have absolutely no\n>    knowledge of the target. IOW, we don't know that one invocation of\n>    {{component is for a Ember.Component and another is for a\n>    Ember.GlimmerComponent.\n>    - At runtime after auto-(mut has been applied, we have no way\n>    currently to know if (mut was added by the auto-mut infrastructure or\n>    by the user in their template. This means that we cannot make\n>    {{component or (component \"fix\" (by removing the mutable object) the\n>    attrs. This could be fixed by adding a flag to (mut in the auto-mut.\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/emberjs/ember.js/issues/12590#issuecomment-156539889>.\n>\n"}}