Schematic for Angular Material Dialog

[marc-wilson]

Feature Description

Provide a brief summary of the feature you would like to see.
I find the setup process of components to be quite redundant in some cases. An example is creating a dialog. I see that angular material has schematics. It would be nice if there was something for a dialog:
ng generate @angular/material:dialog <component-name>

This would generate a component like so:

import { Component, Inject, OnInit } from '@angular/core';
import { MAT_DIALOG_DATA, MatDialogRef } from '@angular/material';

@Component({
  selector: 'app-aggregate-dialog',
  templateUrl: './aggregate-dialog.component.html',
  styleUrls: ['./aggregate-dialog.component.scss']
})
export class AggregateDialogComponent implements OnInit {
  private _dialogRef: MatDialogRef<AggregateDialogComponent>;
  constructor(dialogRef: MatDialogRef<AggregateDialogComponent>, @Inject(MAT_DIALOG_DATA) data: any) {
    this._dialogRef = dialogRef;
  }

  ngOnInit() {
  }

}

This would also mean the dialog component would be added to the entryComponents in the module.

Use Case

Describe the use case(s) that the proposed feature would enable.
For dialog-heavy applications, setting up dialogs require quite a few steps. It would be nice if this was a little more streamlined. Given that (I believe) if you want to use an Angular Material dialog, it requires it's own component I think it would be useful for the proper (or common) references to be added when generated. It sounds like the entryComponents step won't be needed in v9, so that is nice.

[crisbeto]

For the record, the step about adding it to entryComponents won't be necessary with Ivy.

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.