feat(MatDatepicker): Expose access to MatCalendar used in MatDatepicker

Feature Description

Expose access to MatCalendar instance that is created under the hood when using datepicker.

Use Case

I have requirement to allow user to type into the input date in proper format, and if datepicker is opened, it should update its state by showing typed in date. This is not possible using current api state. What I do now, is a nasty hacking - accessing private members of datepicker.

so, in my component, I have to

  get calendar(): MatCalendar<Date> | undefined {
    // this is soooo baaad and soo hacky to get that calendar instance...... 
    // moreover, calendar can actually be null - when its closed.
    // @ts-ignore
    return this.datepicker._popupComponentRef?.instance._calendar;
  }

     this.myInputField.valueChanges.pipe(filter(v => v), debounceTime(250)).subscribe(v => {
      const calendar = this.calendar;
      // console.log('dp', this.datepicker);
      // console.log('cal', this.calendar);
      //sooooooooo much haaaaaaaaaaaxing
      if (calendar) {
        calendar.activeDate = v;
      }

I think its perfectly valid to manipulate calendar state from the component code. This will obviously stop working when I swtich to touchUI. Therfore, API that provides reliable way to access calendar would be even more convinient.

[crisbeto]

This sounds reasonable, although as you mentioned, the calendar being null while it’s closed is a little weird. I’m not sure I follow the use case that you’re describing though. The calendar should be set up to reflect the date that’s been typed into the input already.

[angular-robot[bot]]

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.