Conversation
| // Set any properties with this.set('myProperty', 'value'); | ||
| // Handle any actions with this.on('myAction', function(val) { ... }); | ||
|
|
||
| this.render(hbs`{{x-button}}`); |
There was a problem hiding this comment.
@GavinJoyce shouldn't this be {{mu-first-post:x-button}} ?
There was a problem hiding this comment.
or whatever the namespace syntax is 😖
There was a problem hiding this comment.
the test seems to fail with {{mu-first-post:x-button}}:
There was a problem hiding this comment.
So I think this might have something to do with the resolver 🤔 I'm not even sure if the work myself and @rwjblue did even touched on exporting non "main" components in the way that the resolver is expecting (I'm not even sure I'm saying it right there)
There was a problem hiding this comment.
I've just had a look back at what we're doing and I remember now 🎉 the dummy app in this addon is intended to be a test of the new MU addon being included into a classic app. The ember-cli version we're using makes use of the (broccoli-module-unification-reexporter)[https://github.com/ember-cli/ember-cli/blob/mu-addons/package.json#L54) plugin that re-exports the components as "non namespaced" components.
I don't know the best way to proceed 😕
There was a problem hiding this comment.
Thanks. My aim here was to discover what was needed for tests in an addon. I think I've learned enough to apply this to the ember g component blueprint
Uh oh!
There was an error while loading. Please reload this page.