docs(datepicker): add docs for custom calendar header #10543
Conversation
mmalerba
added
pr: needs review
docs
googlebot
added
the
cla: yes
| @@ -287,6 +287,20 @@ export class MyApp {} | |||
|
|
|||
| <!-- example(datepicker-formats) --> | |||
|
|
|||
| #### Customizing the calendar header | |||
|
|
|||
| The header section of the calendar (the part containing the view switcher and previous and next | |||
There was a problem hiding this comment.
Maybe not the right time to ask this question, but why an API that takes a component as an input? We don't have any APIs like that elsewhere in the library, instead using templates and/or content projection.
There was a problem hiding this comment.
Content projection wasn't feasible because it would have had to be passed through several layers <mat-datepicker> --> <mat-datepicker-content> --> <mat-calendar>. A template may have been workable, but there's a fair chunk of logic that goes with the header so a component seemed cleaner. At some point I want to break the datepicker into a bunch of composable pieces, we may be able to change how this works at that point
jelbourn
added
pr: lgtm
action: merge
|
@mmalerba can you rebase? |
|
Done |
|
the header example is not working on docs, i got this error in stackblitz: |
|
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. |
No description provided.