fix(angular): import paths for child components

[sean-perkins]

Description

Provides a default importMapper to the Angular generator to generate valid import statements for Angular module projects.

For example, when importing a child component called ChildComponent, the import path will be generated as:

import { ChildComponentModule } from './child';

I opted against assigning the importMapper to the DEFAULT_OPTIONS, since the function needs context to whether the user has selected to generate for standalone components or not. With standalone enabled, the import mapper should not rewrite the import value to include the Module postfix.

Resolves #1205

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
mitosis-fiddle	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 22, 2023 2:44am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 3e4b8a7. 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 4 targets

• nx build @builder.io/mitosis-fiddle
• nx build @builder.io/eslint-plugin-mitosis
• nx build @builder.io/mitosis
• nx run-many --skip-nx-cache --target build --parallel 4 --exclude */e2e-alpine,*/e2e-angular,@builder.io/mitosis-fiddle,@builder.io/talk-*,@builder.io/example-apps

---

Sent with 💌 from NxCloud.

[samijaber]

Awesome! Make sure to:

• run yarn snapupdate in packages/core to update snapshots.
• run yarn fmt:prettier in the root dir to format the PR.

[samijaber]

I think you're missing wrapping brackets { }, right now the PR imports the same default output, just under a different name. I don't think this is what you want?

Is this what's needed instead?

Suggested change

	return `import ${importValue} from '${importPath}';`;
	return `import {${importValue}} from '${importPath}';`;