-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Dialog Service Docs Need Updated: AOT & EntryComponent #8102
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
Comments
I added the entryComponents in AppModule and everything started working fine. Your docs need updated because I am not using AOT and the entryComponent solved the issue. |
It's being tracked in docs repo: angular/material.angular.io#228 |
@tommyc38 is this issue about the plunker example or the actual |
@jelbourn The docs state that you only need to add in entryComponents for AOT. I am using JIT and the only way it works is by adding in entryComponents. I think the docs need to simply say to add in entryComponents to your NgModule. I spent a few hours wondering why MatDialog did not work. I would like to help someone else avoid the same issue given its not very clear how to get it working IMHO. Thanks. |
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. |
Bug, feature request, or proposal:
The dialog component is not working. It doesn't appear to inject the component.
What is the expected behavior?
I would expect the dialog component to work as per the documentation.
What is the current behavior?
See StackBlitz example.
What are the steps to reproduce?
Providing a StackBlitz/Plunker (or similar) is the best way to get the team to see your issue.
Plunker starter (using on
@master
): https://goo.gl/DlHd6UStackBlitz starter (using latest
npm
release): https://goo.gl/wwnhMVhttps://stackblitz.com/edit/angular-material2-issue-hdwz9o
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: