Bug/Proposal.
The listed propeties/methods have no docs.
Here's the list that I found of all missing docs.
| Class | Properties | Methods |
| ------------- | ------------- | -------------
| MatAutocompleteTrigger |autocomplete, panelOpen
| MatChip | ariaSelected |
| MatChipInput | focused | focus
| MatChipList | controlType , ngControl, role | onContainerClick, setDescribedByIds
| MatDialogClose | dialogRef
| MatDialogRef | id
| MatDialogTitle | id
| MatDatepickerInput | | registerOnValidatorChange, validate
| MatExpansionPanelHeader | panel
| MatError | id
| MatInput | empty, ngControl, shouldLabelFloat | focus, onContainerClick, setDescribedByIds
| MatListOption | selectionList
| MatSelect | ngControl, shouldLabelFloat
| MatSlideToggleChange | All MatSlideToggleChange properties |
| SimpleSnackBar | snackBarRef
Related to #8789.
I noticed that some properties/methods are inherited from a parent class. Is there a way to get the docs copied from there instead of maintain two EQUAL docs?
Good news PR #9299 is fixing this.
AFAIK that PR is only related for some missing docs, not all.
Every member that is inherited is now showing up in the docs. If you still see some members that are not showing up properly, please file a new issue/or respond here and cc. me. Thanks!
@DevVersion I guess you solved part of the "problem". This issue doesn't consists only about inherited members. There are a few members (in table that I listed) that are still undocumented and aren't inherited from anywhere.
It'd be great if you reopen this issue.
By the way, do you mind if I send separate PRs to fix some of them?
@rafaelss95 That might be true. I didn't specifically look at all members in the table you posted, because I thought it was also about the inherited members.
And sure, please go ahead and submit a PR. For such small changes It would be better to just have one PR for all members.
Does anyone here know how to use 'shouldLabelFloat' on a MatInput?
Completely lost, docs are useless.
@DevVersion:
ExpansionPanel:
expanded is declared like this:
Is there a specific reason to it be declared this way, instead of the _usual_ @Input()? I'm asking because this way, AFAIK, it can't be documented.
Sort:
matSortDisabled is declared like this:
...however it appears as disabled in docs.
Also, all the inputs declared in Component/Directive _metadata_ appear without @Input() decorated. Is it the expected behavior?
How can one hide the updateErrorState from the docs? (For example in MatSelect.) From what I understand this should not be part of the public API.
Most helpful comment
Does anyone here know how to use 'shouldLabelFloat' on a MatInput?
Completely lost, docs are useless.