feat(table): add text column for simple columns

[andrewseguin]

Adds an easier way to add columns to the table for cases where the cells are simply text values.

Rather than writing this:

<ng-container matColumnDef="score">
  <th mat-header-cell *matHeaderCellDef> Score </th>
  <td mat-cell *matCellDef="let user"> {{user.score}} </td>
</ng-container>

you can instead write:

<mat-text-column name="score"></mat-text-column>

For simple cases, and for users that just want to quickly bring up a table and iterate, this is much easier to write and remember.

Considerations: Do we need to add a mat-number-column? The only difference will be that it would default to justify="end".

Fixes #9925

[jelbourn]

I'm not sure we should default to using the column name for property access because it's just setting people up for production bugs when the property name is minified.

[andrewseguin]

I'd prefer to lean towards leaving the behavior as is, but make sure to mention in the documentation that this may come up. I suspect it is very rare for users to have minified properties on their table data and the added API requirement will seem very redundant for everyone else.

We do something similar in the MatTableDataSource where, by default, the sort accessor (sortingDataAccessor) uses property access by the sort header ID which will have the same minification problems. I haven't seen any issues come in regarding confusion about it.

Happy to chat more about it in case I misunderstand how often this would occur

[jelbourn]

Okay- can you add the documentation in this PR?

[jelbourn]

Should there be an error if there's no table instance?

[andrewseguin]

Sure - I can't think of a good reason why it'd be useful otherwise.

[jelbourn]

Overall looks good aside from documentation for that property renaming concern

[andrewseguin]

Added noted saying you should use the data accessor if your data may be minified - feel free to suggest other wording

[jelbourn]

LGTM

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}