Feature Request: Allow to generate libraries within a particular folder & allow to rename 'projects' folder name

[micronyks]

Bug Report or Feature Request (mark with an x)

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

Command (mark with an x)

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

Versions

Latest

Desired functionality

Currently It is not possible to generate a library within a specific folder with relative path.
When I run ng generate library mylib --prefix=mylib command, it generates a folder called projects under root directory and places mylib under projects

Current Flow,

|---MyFoodApplication
|                    |---projects
|                                |---mylib-1
|                                |---mylib-2
|                    |---src

Sometimes use-case can be like:

1. Create all libraries under common folder resides at (anywhere) angular project's root directory. (common is just a folder and nothing else)

2. When I want to create any library, It should create desire name of the folder (eg. companyname-libraries) which must contain all generated library.

So, the final output should be like below,

|---MyFoodApplication
|                    |---common
|                              |---companyname-libraries
|                                                       |---mylib-1
|                                                       |---mylib-2
|                    |---src

[jorroll]

Obviously this isn't ideal, but I work around this issue by simply updating the angular.json "newProjectRoot" property to be whatever I want for the project I'm generating at that moment.

In general, I keep it at the project root for my libraries (because I generate more of those) and I temporarily change it to the project root for my apps when I need to generate a new app (and then immediately change it back to my libraries' project root).

[micronyks]

@thefliik I have already done it but it should not be a manual process ! That's why I've added this as a feature request.

[emirhg]

It's been two years and this issue remains open. I'll like to work on it as I'll find it very useful on a current project. So far I've identified the involved line:

angular-cli/packages/schematics/angular/library/index.ts

Line 153 in 9ee905d

const newProjectRoot = workspace.extensions.newProjectRoot as (string | undefined) || '';

I'm thinking on a CLI argument like ng generate library my-lib --newProjectRoot=my-prefix-path in order to be consistent with the JSON config file. Would love to read your comments about it

[angular-robot]

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]

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-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}