Adding in Type support for standardized prop interfaces

[iryanclarke]

Adds in essentially what we already have within hw-admin for our shared interfaces, and also adds in the typing for individual profiles themselves (aka primary, and info)

Does all of these additions make sense?

[CCAyl]

i was wondering if we need to still have these typed out, i'm assuming the profile mapper was also giving you heck?

[CCAyl]

i guess we also just need to this move over our colour prop types

[iryanclarke]

i was wondering if we need to still have these typed out, i'm assuming the profile mapper was also giving you heck?

The profile mapper is working great! I mostly need the typing for the individual color profiles like primary so I can properly type the mapping style functions, similar to how we currently have them:

const colorProfileStyles => (selectedColor: colorTheme) => css`
     color: ${selectedColor.base};
     background-color: ${selectedColor.backgroundMuted};
`

[CCAyl]

if mapper is working great for you i have other questions, because mine completely blew up storybook lol

[alexandra-lim]

if mapper is working great for you i have other questions, because mine completely blew up storybook lol

Yeah Cath and I were looking at mapper yesterday and couldn't figure it out. Can you link us to an MR you've implemented it in?