Skip to content
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

Run schematic task in child directory. #12915

Closed
Bored-Bohr opened this issue Nov 9, 2018 · 3 comments
Closed

Run schematic task in child directory. #12915

Bored-Bohr opened this issue Nov 9, 2018 · 3 comments
Labels
area: @angular-devkit/schematics feature: insufficient votes Label to add when the not a sufficient number of votes or comments from unique authors feature Issue that requests a new feature
Milestone

Comments

@Bored-Bohr
Copy link

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

Command (mark with an x)

- [x] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

node: v8.12.0
npm: 6.4.1
Angular CLI: 7.0.4
OS: win32 x64 (OS Build 14393.2551)

Repro steps

context.addTask(new RunSchematicTask(schematicName, options));

Desired functionality

I believe that it would be useful to be able to execute a schematic task from the child directory. Currently, new RunSchematicTask generates a HostTree from the current host and transfers the parentContext.

It would be useful for a case such as running a schematic in ng-new as a task that installs dependencies and calls _readPackageJson which relies on an absolute path for the package.json.

@clydin clydin added feature Issue that requests a new feature area: @angular-devkit/schematics labels Nov 9, 2018
@ngbot ngbot bot added this to the Backlog milestone Nov 9, 2018
@angular-robot
Copy link
Contributor

angular-robot bot commented Feb 1, 2022

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

@angular-robot angular-robot bot added the feature: votes required Feature request which is currently still in the voting phase label Feb 1, 2022
@ngbot ngbot bot modified the milestones: Backlog, needsTriage Feb 1, 2022
@angular-robot
Copy link
Contributor

angular-robot bot commented Feb 21, 2022

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

@angular-robot angular-robot bot added feature: insufficient votes Label to add when the not a sufficient number of votes or comments from unique authors and removed feature: votes required Feature request which is currently still in the voting phase labels Feb 21, 2022
@alan-agius4
Copy link
Collaborator

Closing this as it does not fall within the current scope.

@alan-agius4 alan-agius4 closed this as not planned Won't fix, can't repro, duplicate, stale Apr 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: @angular-devkit/schematics feature: insufficient votes Label to add when the not a sufficient number of votes or comments from unique authors feature Issue that requests a new feature
Projects
None yet
Development

No branches or pull requests

3 participants