Angular2 material dialog has issues - Did you add it to NgModule entryComponents

Question

I am trying to follow the docs on https   material angular io components component dialog but I cannot understand why it has the below issue   I added the below on my component    Component     selector   dialog-result-example-dialog     templateUrl     dialog-result-example-dialog html      export class DialogResultExampleDialog     constructor public dialogRef  MdDialogRef lt DialogResultExampleDialog gt          In my module I added   import   HomeComponent DialogResultExampleDialog   from    home home component     NgModule     declarations        AppComponent      LoginComponent      DashboardComponent      HomeComponent      DialogResultExampleDialog                Yet I get this error      EXCEPTION  Error in   HomeComponent class HomeComponent - inline template 53 0 caused by  No component factory found for DialogResultExampleDialog  Did you add it to  NgModule entryComponents      ErrorHandler handleError   error handler js 50     next   application ref js 346     schedulerFn   async js 91     SafeSubscriber   tryOrUnsub   Subscriber js 223     SafeSubscriber next   Subscriber js 172     Subscriber  next   Subscriber js 125     Subscriber next   Subscriber js 89     Subject next   Subject js 55     EventEmitter emit   async js 77     NgZone triggerError   ng zone js 329     onHandleError   ng zone js 290     ZoneDelegate handleError   zone js 246     Zone runTask   zone js 154     ZoneTask invoke   zone js 345     error handler js 52 ORIGINAL EXCEPTION  No component factory found for DialogResultExampleDialog  Did you add it to  NgModule entryComponents      ErrorHandler handleError   error handler js 52     next   application ref js 346     schedulerFn   async js 91     SafeSubscriber   tryOrUnsub   Subscriber js 223     SafeSubscriber next   Subscriber js 172     Subscriber  next   Subscriber js 125     Subscriber next   Subscriber js 89     Subject next   Subject js 55     EventEmitter emit   async js 77     NgZone triggerError   ng zone js 329     onHandleError   ng zone js 290     ZoneDelegate handleError   zone js 246     Zone runTask   zone js 154     ZoneTask invoke   zone js 345

User · Answer

In case of lazy loading  you just need to import MatDialogModule in lazy loaded module  Then this module will be able to render entry component with its own imported MatDialogModule    NgModule     imports       MatDialogModule        declarations        AppComponent      LoginComponent      DashboardComponent      HomeComponent      DialogResultExampleDialog                entryComponents   DialogResultExampleDialog

User · Answer

You need to add dynamically created components to entryComponents inside your  NgModule   NgModule     declarations        AppComponent      LoginComponent      DashboardComponent      HomeComponent      DialogResultExampleDialog                entryComponents   DialogResultExampleDialog    Note  In some cases entryComponents under lazy loaded modules will not work  as a workaround put them in your app module  root

User · Answer

I had the same issues and i had dialogComponent in EntryComponents and it still did not work  this is how I was able to solve the problem  the link is here to a previously answered post  https   stackoverflow com a 64224799 14385758

User · Answer

If someone needs to call Dialog from services here is how to solve the issue  I agree with some of above answer  my answer is for calling dialog in services if someone may face issues on   Create a service for example DialogService then move your dialog function inside the services and add your dialogservice in the component you call like below code     Component     selector   app-newsfeed     templateUrl     abc component html     styleUrls      abc component css       providers  DialogService       otherwise you get error

User · Answer

In my case  I added my component to declarations and entryComponents and got the same errors  I also needed to add MatDialogModule to imports

User · Answer

While integrating material dialog is possible  I found that the complexity for such a trivial feature is pretty high  The code gets more complex if you are trying to achieve a non-trivial features   For that reason  I ended up using PrimeNG Dialog  which I found pretty straightforward to use   m-dialog component html    lt p-dialog header  Title  gt    Content  lt  p-dialog gt    m-dialog component ts    Component     selector   m-dialog     templateUrl   m-dialog component html     styleUrls      m-dialog component css      export class MDialogComponent        dialog logic here     m-dialog module ts   import   NgModule   from   angular core   import   CommonModule   from   angular common   import   DialogModule   from  primeng primeng   import   FormsModule   from   angular forms     NgModule     imports        CommonModule      FormsModule      DialogModule         exports        MDialogComponent          declarations        MDialogComponent        export class MDialogModule      Simply add your dialog into your component s html    lt m-dialog  isVisible   true  gt   lt  m-dialog gt    PrimeNG PrimeFaces documentation is easy to follow and very precise

User · Answer

If you are like me  and are staring at this thread thinking  But I m not trying to add a component  I am trying to add a guard service pipe  etc   then the issue is likely that you have added the wrong type to a routing path  That is what I did  I accidentally added a guard to the component  section of a path instead of the canActivate  section  I love IDE autocomplete but you have to slow down a bit and pay attention  If you absolutely can t find it  do a global search for the name it is complaining about and look at every usage to make sure you didn t slip-up with a name

User · Answer

This is happening because this is a dynamic component and you didn t add it to entryComponents under  NgModule   Simply add it there    NgModule        -----------------      entryComponents    DialogResultExampleDialog       lt ---- Add it here   Look at how the Angular team talks about entryComponents      entryComponents   Array lt Type lt any gt  any   gt  Specifies a list of   components that should be compiled when this module is defined  For   each component listed here  Angular will create a ComponentFactory and   store it in the ComponentFactoryResolver    Also  this is the list of the methods on  NgModule including entryComponents     As you can see  all of them are optional  look at the question marks   including entryComponents which accept an array of components    NgModule      providers   Provider     declarations   Array lt Type lt any gt  any   gt    imports   Array lt Type lt any gt  ModuleWithProviders any   gt    exports   Array lt Type lt any gt  any   gt    entryComponents   Array lt Type lt any gt  any   gt    bootstrap   Array lt Type lt any gt  any   gt    schemas   Array lt SchemaMetadata any   gt    id   string

User · Answer

If you re trying to use MatDialog inside a service - let s call it  PopupService  and that service is defined in a module with    Injectable   providedIn   root       then it may not work  I am using lazy loading  but not sure if that s relevant or not   You have to    Provide your PopupService directly to the component that opens your dialog - using   provide  PopupService    This allows it to use  with DI  the MatDialog instance in the component  I think the component calling open needs to be in the same module as the dialog component in this instance  Move the dialog component up to your app module  as some other answers have said  Pass a reference for matDialog when you call your service    Excuse my jumbled answer  the point being it s the providedIn   root  that is breaking things because MatDialog needs to piggy-back off a component

User · Answer

You need to use entryComponents under  NgModule   This is for dynamically added components that are added using ViewContainerRef createComponent    Adding them to entryComponents tells the offline template compiler to compile them and create factories for them   The components registered in route configurations are added automatically to entryComponents as well because router-outlet also uses ViewContainerRef createComponent   to add routed components to the DOM   So your code will be like   NgModule     declarations        AppComponent      LoginComponent      DashboardComponent      HomeComponent      DialogResultExampleDialog                entryComponents   DialogResultExampleDialog

User · Answer

You must add it to entryComponents  as specified in the docs    NgModule     imports                      entryComponents        DialogInvokingComponent       DialogResultExampleDialog        declarations        DialogInvokingComponent         DialogResultExampleDialog                    Here is a full example for an app module file with a dialog defined as entryComponents

[angular] Angular2 material dialog has issues - Did you add it to @NgModule.entryComponents?

Examples related to angular

Examples related to angular-material