-
Notifications
You must be signed in to change notification settings - Fork 138
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
Can't resolve components for integration tests #113
Comments
Sounds like an issue with how the test's import Resolver from '../../resolver';
import config from '../../config/environment';
const resolver = Resolver.create();
resolver.namespace = {
modulePrefix: config.modulePrefix,
podModulePrefix: config.podModulePrefix
};
export default resolver; You'll want to make sure the So in other words, make sure the Bonus tip: the reason you see |
For anyone else encountering this issue:
We haven't thought of a way to avoid hard-coding |
Thanks for the update @cklimkowsky
As of ember-engines v0.2.5 (from the v0.2 branch), you should be able to import the same |
@dgeb we can import it everywhere without issues EXCEPT in We are using Ember 2.7.0-canary :-/ |
How would this be fixed with |
When I run
ember g component foo-component
, it generates a file within the addon and app directories. When I try to run the generated test, it fails, saying it can't find the module. When I delete the component from the app directory (since it's my understanding an engine shouldn't have an app directory in the first place), the test interprets the component as a helper and says it can't be found.I've only encountered this issue with components so far, not sure if the same thing happens with routes, models, etc.
Are there issues with tests at this point, or is there something I'm missing? Thank you!
@Kaceykaso
The text was updated successfully, but these errors were encountered: