search

OfficeDev / microsoft-teams-ui-component-library

Component library enhanced experiences styled for use in Microsoft Teams custom applications.
MIT License
127 stars 30 forks source link

Component naming #2

Open thure opened 3 years ago

thure commented 3 years ago

Currently components with names like Toolbar exist in both Fluent UI and as a "high-value" component for Teams.

Will developers benefit from working with different names, or should naming overlap intentionally?

Furthermore, what are our conventions around component names that are more than one word, i.e. how will we disambiguate between a part of a high-value component and an unrelated first-class high-value component, e.g. between "task board" and a hypothetical component called "board", given patterns like Table (an HVC) and TableRow (a special component of Table) are accepted?