-
Notifications
You must be signed in to change notification settings - Fork 12k
Generating Blueprints in directory other than src/app #5995
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
Comments
There's a couple of things in this issue:
|
looks like #6079 fixes this |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug Report or Feature Request (mark with an
x
)I posted the following question on gitter:
@hansl was kind enough to respond:
@hansl that's nice for apps that are bootstrapped. But if someone is working on let's say a library that's bootstrapped only in unit tests, then that will be problematic, unless you are incorporating that into your plans somehow?
I think its not a bad idea to just have an extra configuration in
.angular-cli.json
to simply change the default name from "app".Another alternative resolution for the meantime, is to allow the following to command to work
ng generate directive mydirname --export --module="../lib/mylib.module"
It current results in the error:
Invalid path: "../lib/quill.module.ts" cannot be above the "src/app" directory
Ultimately I could see having multiple sibling source directories at "src/*" level such some subset of :
["app", "browser", "server", "common", "android", "ios", "webworker" , "lib"]
(I'll call these "ngRoots", so for example the ngRoot directory
server
is located at "src/server")It would be nice to have the ability to generate blueprints by specifying relative which
ngRoot
directory they should generated in. e.g.ng generate directive mydirname --export --module="./mylib.module" --ngRoot="./lib"
Thought?
The text was updated successfully, but these errors were encountered: