proposal(mat-button): rename mat-button directive to matButton

Bug, feature request, or proposal:

proposal

What is the expected behavior?

The mat-button directive should conform to the angular style guide and have a name in lowerCamelCase: matButton

<button matButton></button>

What is the current behavior?

The mat-button directive does not conform to the angular style guide

<button mat-button></button>

What is the use-case or motivation for changing an existing behavior?

Conform angular material2 to the angular style guide

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

angular 4.4.6 material 2-beta.12

[fxck]

You can’t have button inside an anchor. And when it comes to “applying routerLink attribute to it”, that wouldn’t work, you can’t internally switch between anchor and button element based on just that, since routerLink listens to click event, you can in theory use it on buttons as well. And as I mentioned, you’d have to manually add all the attributes native elements might have and then pass them down to underlying elements (think disabled for example). It’s far better to simply have an attribute component.

[angular-automatic-lock-bot[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.}