-
Notifications
You must be signed in to change notification settings - Fork 395
bug(plunker): fix plunkers not working with dialogs #5899 #228
Conversation
@amcdnl, I haven't seen any mention in the code to the |
@tinayuangao is better to review since she authored the plunker generation |
// Replace `declarations: [MaterialDocsExample]` | ||
// will be replaced as `declarations: [ButtonDemo]` | ||
fileContent = fileContent. | ||
replace(/declarations: \[MaterialDocsExample\]/g, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also replace entryComponents
?
Add entryComponents: [MaterialDocsExample]
to main.ts
.
I tested on plunker and found out it doesn't work without entryComponents.
@tinayuangao - Is this PR still relevant. Looks like they are working today. |
@amcdnl, @tinayuangao, dialogs are still throwing exceptions (lack of entryComponents). |
@julianobrasil where are you seeing it throwing the errors? |
@amcdnl, if you click on the link to the plunk example for the dialogs (at https://material.angular.io/components/dialog/overview), you'll see the errors: Notice that the |
Closing this since it outdated, will update in a new PR. |
Resolved here - #356 |
Fixes: angular/components#5899