Allow componentFactoryResolver to be passed to MatDialog.open

[scriby]

Feature Description

The portal made by MatDialog always defaults to the root component factory resolver, which means any dynamically rendered components must be registered in the root component. This seems to cause a lot of confusion (#1491, #8473) and lots of stack overflow posts.

Having to declare these components in the root module is bad for modularity and code splitting. It seems that if we could provide the component factory resolver to the portal (similar to how the viewContainerRef is provided for the injector), then it would be possible to define the dynamically created entryComponents in modules closer to where they're used.

See

components/src/material/dialog/dialog.ts

Lines 268 to 269 in 94ad613

	const contentRef = dialogContainer.attachComponentPortal<T>(
	new ComponentPortal(componentOrTemplateRef, undefined, injector));

. This code path is both not using the passed in viewContainerRef, and it also doesn't provide a componentFactoryResolver to the portal.

Use Case

Support lazy loaded dialog components, allowing for better code modularity and more precise code splitting.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}