fix(angular): remove double normalize of project name #11819

[Coly010]

Current Behavior

We were adding a secondary normalization of the project name when generating a standalone component for a standalone library when a directory was passed. This caused an unexpected error by adding the directory name again.

Expected Behavior

Should generate a standalone library with component with no errors when a directory is passed

Related Issue(s)

Fixes #11819

[nx-cloud-staging]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit c2eec30. 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 12 targets

• nx affected --target=e2e --base=a2647549d4047b0994138e010e14a1a5a7ed2481 --head=c2eec3060144e942180719d06ac6e5abdde28eca --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox,e2e-make-angular-cli-faster --parallel=1
• nx affected --target=test --base=a2647549d4047b0994138e010e14a1a5a7ed2481 --head=c2eec3060144e942180719d06ac6e5abdde28eca --parallel=1
• nx affected --target=build --base=a2647549d4047b0994138e010e14a1a5a7ed2481 --head=c2eec3060144e942180719d06ac6e5abdde28eca --parallel=3
• nx-cloud record -- yarn depcheck
• nx affected --target=lint --base=a2647549d4047b0994138e010e14a1a5a7ed2481 --head=c2eec3060144e942180719d06ac6e5abdde28eca --parallel=3
• nx-cloud record -- yarn nx workspace-lint
• nx-cloud record -- yarn check-lock-files
• nx-cloud record -- yarn check-commit
• nx-cloud record -- yarn nx format:check --base=a2647549d4047b0994138e010e14a1a5a7ed2481 --head=c2eec3060144e942180719d06ac6e5abdde28eca
• nx-cloud record -- yarn check-imports
• nx-cloud record -- yarn documentation
• nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Updated
nx-dev	⬜️ Ignored (Inspect)		Sep 1, 2022 at 10:02AM (UTC)

[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.