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
Library schematic does not support path property #16080
Comments
I'm bumping into the same issue for any schematic dev work trying to use the Angular Schematics config getWorkspacePath method - they'r blowing up in test runs and dev work no matter what work arounds I try to implement |
+1 |
Same here.
|
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. |
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. |
I have the same problem, any update? |
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Not as far as I know
Description
I tried to create a schematic that generates an application and adds a library to it. However, the library schematic does not accept a
path
as parameter and it then attempts to create the library in the folder that contains the application. Specifically, it tries to read theangular.json
file from the folder containing the application folder (e.g. the folder where the schematic is run).Note that I expected the
path
property to work, as it's included with most of the other Angular schematics, for example component, module and service.🔬 Minimal Reproduction
A minimal reproduction may be found in this repo.
It also addresses a problem I had when trying to work around this with
applyToSubtree
.Here is the simplest description I could come up with.
Given this factory:
If you execute the schematic in a folder named
/parent/folder
and the app generates in a new folder named app (/parent/folder/app
), the library schematic searches for theangular.json
in/parent/folder
instead of/parent/folder/app
.🔥 Exception or Error
🌍 Your Environment
Similar issues
#17598
The text was updated successfully, but these errors were encountered: