fix(angular): handle not provided path when generating a component without the project option

[leosvelperez]

Current Behavior

Generating a component from the workspace root without providing the project and path options throws an error.

Expected Behavior

Generating a component from the workspace root without providing the project and path options should not throw and fallback to use the set defaultProject. Only if defaultProject is not set we throw a meaningful error to the user.

Related Issue(s)

Fixes #13874

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated
nx-dev	⬜️ Ignored (Inspect)		Dec 17, 2022 at 11:06AM (UTC)

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 7f62377. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 11 targets

• nx affected --target=e2e --base=78f3a3cf16c36538d4ce33ab61c81622a7c4a95f --head=7f6237795c40825d9052e2970e995ab1b0f307ef --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox --parallel=1
• nx affected --target=test --base=78f3a3cf16c36538d4ce33ab61c81622a7c4a95f --head=7f6237795c40825d9052e2970e995ab1b0f307ef --parallel=1
• nx depcheck --no-dte
• nx affected --target=build --base=78f3a3cf16c36538d4ce33ab61c81622a7c4a95f --head=7f6237795c40825d9052e2970e995ab1b0f307ef --parallel=3
• nx affected --target=lint --base=78f3a3cf16c36538d4ce33ab61c81622a7c4a95f --head=7f6237795c40825d9052e2970e995ab1b0f307ef --parallel=3
• nx lint --no-dte
• nx check-lock-files --no-dte
• nx check-commit --no-dte
• nx-cloud record -- nx format:check --base=78f3a3cf16c36538d4ce33ab61c81622a7c4a95f --head=7f6237795c40825d9052e2970e995ab1b0f307ef
• nx check-imports --no-dte
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[Coly010]

LGTM!

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.