Priority of Components about ember-polaris HOT 5 CLOSED

@andrewpye let's keep items unchecked until they are merged, so when checked they are usable. Instead for the ones that are ready and just waiting for review link to the PR from that item

from ember-polaris.

@robinsharma I think we're going to need the Page component too right? I currently have a hopefully MVP of that sitting on a branch, I'll put a PR in for it shortly.

from ember-polaris.

@robinsharma I think the titles and text components are worth implementing where we need them, they're generally relatively quick and painless to put together. I've already got Display text, Heading and Subheading components merged down to master, and from a quick flick through the mockups it looks like we don't need any others. We already export the Polaris SASS from this addon so unless I'm missing something we should be good to go on the typography side of things, right?

A point here is that in browsing the code rendered by the React components, internally some of them use other React components. I've just put in a PR for the Card component and internally it uses the Heading and Subheading components. In cases like this when we need the functionality, I think it's worth implementing an MVP of whichever components are used internally by other components so that we don't build up tech debt.

from ember-polaris.

@vladucu good point, thanks!

from ember-polaris.

Closing this as we've built out everything we need at this point

from ember-polaris.