-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Schematics: Support --project flag to specify apps or libs #1455
Comments
I need the same thing |
Sounds good to me. The workaround today is to change the |
@brandonroberts the workaround make sense but doesn't works for me with Angular/CLI 7. I had already tried before post the issue. I will work on it this week to make the PR. Some tip to work on it? |
@rafa-as Thanks for working on this! Each schematic has a schema that is represented through JSON and TypeScript. I'll use the container as an example, because the other schematics will follow the same structure. Container schema JSON: Container schema TypeScript The Once you add the Here is an example test with a specified project you can reference to add tests to each schematic: If you need more assistance, just let us know. |
Now its possible to specify the project when generate actions, effects, entities, features, reducers and stores. The new flag is --project and his alias -p Upgrade the documentation to add the new flag and his alias Closes ngrx#1455
@brandonroberts PR done! :) |
Describe any alternatives/workarounds you're currently using
Now it's impossible to generate a feature, store, reducer, entity, action and effect in a specific app or lib. To do this very common task we should create it in the default app and move it to the correct app.
Only container, because generates a component, supports the project flag.
Other information:
Angular CLI accepts this flag since version 6.
If accepted, I would be willing to submit a PR for this feature
[x] Yes (Assistance is provided if you need help submitting a pull request)
[ ] No
The text was updated successfully, but these errors were encountered: