Cannot unregister component template

[jakedetels]

The Ember.ApplicationInstance#unregister method fails to fully unregister a component template. See twiddle here: https://ember-twiddle.com/47dd2375c095cd7e73e5

I can successfully register a component template using:

let template = Ember.Handlebars.compile('<b>First x-foo</b>');
application.register('template:components/x-foo', template );

However, when I try unregistering this template followed by registering a different compiled template in its place, the original template is the one that gets rendered.

application.unregister('template:components/x-foo');
let newTemplate = Ember.Handlebars.compile('<b>New x-foo</b>');
application.register('template:components/x-foo', newTemplate );

In the twiddle demo, clicking "Register Template" will register the first compiled template. Then, clicking "Change Template" will first unregister the old template, followed by loading a new complied template. Yet when the component template is rendered, we still see the original compiled template. This demo utilizes the {{component}} helper to load the registered component template.

cc @dgeb (possibly related to commit 53267df)

[GavinJoyce]

This behaviour is the same in ember 1.12.1 (twiddle) and 1.13.11 (twiddle).

[GavinJoyce]

https://embercommunity.slack.com/archives/dev-ember/p1454362713000478

[GavinJoyce]

@jakedetels how come you need to unregister a component and replace it at runtime? Can you just register both and use the component helper to switch at runtime?

[pixelhandler]

@jakedetels I think the suggestion by @GavinJoyce makes sense and may be an elegant way to swap the components with the component helper

[pixelhandler]

@mixonic do you think this is a bug?

[mixonic]

As we have no response from @jakedetels, I'm going to provisionally mark this wontfix and close it.

[andyhot]

I believe a valid use-case for this is to support template hot-swapping