i18n

[andreypopp]

i18n should be designed along with component library not as the afterthought.

• Contextual API (<I18N />)
• <Block />
• <Radio />
• <Button /> (iconRight, groupHorizontally)
• <Checkbox />
• <Box />
• Some kind of directional list

cc @jayclassless

[jayclassless]

Agreed. Although I would suggest "in addition to" rather than "instead of", just in case the author absolutely needs to do things in a right/left fashion.

Properties that should be addressed:

• marginLeft/marginRight
• paddingLeft/paddingRight
• left/right
• textAlign
• The "attach" variants of Button

Would we want to get super fancy and try to parse the values of margin and padding so that left/right values are swapped?

[andreypopp]

Would we want to get super fancy and try to parse the values of margin and padding so that left/right values are swapped?

I think it's better not to support shortcut forms at all. That means using margin is only possible if you want all sides have the same margin: margin={10} is ok but margin="10 20" is disallowed.

[jayclassless]

I think it's better not to support shortcut forms at all. That means using margin is only possible if you want all sides have the same margin: margin={10} is ok but margin="10 20" is disallowed.

I think that's fair.

[jayclassless]

Should also address the icon/iconRight props on buttons.