Rename MatTableDataSource to ClientArrayTableDataSource #14378
Labels
area: material/table
feature
This issue represents a new feature or feature request rather than a bug or bug fix
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Comments
jelbourn
added
the
P3
andrewseguin
added
the
feature
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Mar 10, 2019
Renames the `MatTableDataSource` to `ClientArrayTableDataSource` to make it a bit clearer what it's supposed to be used for. Fixes angular#14378.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Mar 10, 2019
Renames the `MatTableDataSource` to `ClientArrayTableDataSource` to make it a bit clearer what it's supposed to be used for. Fixes angular#14378.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Mar 10, 2019
Renames the `MatTableDataSource` to `ClientArrayTableDataSource` to make it a bit clearer what it's supposed to be used for. Fixes angular#14378.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Mar 16, 2019
Renames the `MatTableDataSource` to `ClientArrayTableDataSource` to make it a bit clearer what it's supposed to be used for. Fixes angular#14378.
This was referenced May 13, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I see too frequently people misunderstand the intent behind
MatTableDataSource, thinking that it's meant to be the primary (or only) way to add data to the table. Renaming this, and more eminently presenting it in the docs as just one option would hopefully help clear this up.Obviously this will need to be done in a backwards compatible way. It will also need a migration schematic.
The text was updated successfully, but these errors were encountered: