Ant design is one the design library we use for most of our components. The first antd 5 versions are now two years old, and other AICS repos including Simularium front ends like NBSV use v5.
The primary difference, besides the availability of certain new components and features (Flex, multi value slider, etc) is moving from less to the use of a ConfigProvider with global and component level design tokens, as well as CSS-in-JS approaches. There may component specific changes to props and other implementation details we need to take care of as we migrate.
Hopefully most of our existing components, props, types and CSS modules/selectors will migrate easily, and we can simply find where we need to add styling to account for what ant-vars.less is still doing.
Acceptance Criteria
[ ] #603
[ ] #604
[ ] #605
[ ] fix broken styles
[ ] align CSS vars and theme vars in naming and usage
Use Case
Ant design is one the design library we use for most of our components. The first
antd 5versions are now two years old, and other AICS repos including Simularium front ends like NBSV use v5.The primary difference, besides the availability of certain new components and features (
Flex, multi value slider, etc) is moving fromlessto the use of aConfigProviderwith global and component level design tokens, as well asCSS-in-JSapproaches. There may component specific changes to props and other implementation details we need to take care of as we migrate.Hopefully most of our existing components, props, types and CSS modules/selectors will migrate easily, and we can simply find where we need to add styling to account for what
ant-vars.lessis still doing.Acceptance Criteria
Details