-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Angular should error with the actual config problem if project's root is missing #21310
Closed
2 of 15 tasks
Labels
2022Q3 Fixit
Candidates for the Q3 2022 fix-it
area: @angular/cli
freq1: low
Only reported by a handful of users who observe it rarely
severity1: confusing
type: bug/fix
Milestone
Comments
EvanCarroll
changed the title
Angular should barf with the actual problem if project's root is missing.
Angular should error with the actual config problem if project's root is missing
Jul 8, 2021
alan-agius4
added
area: @angular/cli
freq1: low
Only reported by a handful of users who observe it rarely
severity1: confusing
type: bug/fix
labels
Jul 8, 2021
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Jun 30, 2022
…project has missing `root` property The `root` property is required in a workspace project. Now we issue an actionable error message when this is missing. Closes: angular#21310
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Jun 30, 2022
…project has missing `root` property The `root` property is required in a workspace project. Now we issue an actionable error message when this is missing. Closes: angular#21310
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Jul 7, 2022
…e project has missing `root` property The `root` property is required in a workspace project. Now we issue an actionable warning message when this is missing. Note: this will become an error in the next major version. Closes: angular#21310
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Jul 7, 2022
…e project has missing `root` property The `root` property is required in a workspace project. Now we issue an actionable warning message when this is missing. Note: this will become an error in the next major version. Closes: angular#21310
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Jul 7, 2022
…e project has missing `root` property The `root` property is required in a workspace project. Now we issue an actionable warning message when this is missing. Note: this will become an error in the next major version. Closes: angular#21310
alan-agius4
added a commit
that referenced
this issue
Jul 8, 2022
…e project has missing `root` property The `root` property is required in a workspace project. Now we issue an actionable warning message when this is missing. Note: this will become an error in the next major version. Closes: #21310
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.
Labels
2022Q3 Fixit
Candidates for the Q3 2022 fix-it
area: @angular/cli
freq1: low
Only reported by a handful of users who observe it rarely
severity1: confusing
type: bug/fix
🐞 Bug report
Command (mark with an
x
)Is this a regression?
No, not that I know
Description
If you have more than two projects, and any project lacks
root
you will get the following error onng generate
🔬 Minimal Reproduction
Run
ng g foo
with the followingNote, either
demo-app
andbar
must lackroot
, or both must lackroot
. If only one entry exists and it omitsroot
thenng g
will work as desired.🔥 Exception or Error
An error not about and internal use of pathing.
🌍 Your Environment
The text was updated successfully, but these errors were encountered: