We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
hi,
trying to use ember-can in our app that consists of the main app and a few in-repo-engines.
we have a account-section and a corresponding account permission (read/write)
according to the docs, it should look like this:
// /lib/account/addon/abilities/account.js export { default } from 'merchant-admin/abilities/account';
(merchant-admin is the main app, account is one of the in-repo-engines and account is also the name of the ability created in the main app)
I tried that, but then I'm getting this error:
Uncaught Error: Could not find module account/abilities/account imported from (require)
account/abilities/account
(require)
is it even possible to import from the main app (into the in-repo-engine)? or is there maybe another step missing?
ember: 3.2.2 ember-engines: 0.5.20 ember-can: 1.1.0
The text was updated successfully, but these errors were encountered:
Im not sure if in repo addons have access to the app. They are not engines and they should stay totally independent from the parent
Sorry, something went wrong.
@Exelord not sure I understand, it's a in-repo-engine, why isn't it an engine?
No branches or pull requests
hi,
trying to use ember-can in our app that consists of the main app and a few in-repo-engines.
we have a account-section and a corresponding account permission (read/write)
according to the docs, it should look like this:
(merchant-admin is the main app, account is one of the in-repo-engines and account is also the name of the ability created in the main app)
I tried that, but then I'm getting this error:
is it even possible to import from the main app (into the in-repo-engine)? or is there maybe another step missing?
The text was updated successfully, but these errors were encountered: