Label for each component.

[ahmedshuhel]

Can we have a label for each component? It will make the issue search easier for particular component. e.g. Toast/mdToast, Button etc.

[ThomasBurleson]

I am not sure I understand your request?

[mzbyszynski]

I think he just means adding additional labels to these issues on github, so you could search for all the issues that pertained to mdButton or toast or whatever by looking for a certain label. More of a process request than a feature request, I guess.

[marcysutton]

I accomplish this by using Github's issue search.

[ThomasBurleson]

We will not be adding more Github Issue Labels; we already have 27 labels.

[ahmedshuhel]

@ThomasBurleson, It was a process request as @mzbyszynski said. That's fine. I just have to teach myself how to search github issues more effectively. However, we can add a little convention of prefixing component related issue with the name of the component. e.g. $mdToast: here goes the issue

[ThomasBurleson]

@ahmedshuhel - That is not a bad idea:
e.g.

• (feat(sidenav): add swipe functionality  #35) > mdSideNav: Adding swipe functionality
• (mdTextFloat: does not set required/ng-required #847) > mdTextFloat: does not set required/ng-required

I will update the issues section with this as a recommendation:

Lower camelCase component or service names should prefix the issue title; e.g. <component>: <issue title>

[ahmedshuhel]

@ThomasBurleson Great! a little note about your convention in the README.md would be nice too.