You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @edburyenegren-okta what do you think would be the best way for us to handle this moving forward so we can get the latest and greatest and update the npm package? We could always change cv('gray', '300') to $odyssey-gray-300 and do a mass string replacement (or something like that) but wanted to get your thoughts first.
Hi @dougchan-okta, the upgrade path from that far back is tricky. For folks using the scss package, we highly recommend they use the tokens here instead of referencing colors directly.
However, these tokens will also be refactored with the release of 1.0. After that point, breaking changes should be much less likely.
0.3.0
and relies heavily ongray/300
andgray/400
(but0.3.0
didn't havegray/500
).gray/500
, but the latest_colors.scss
file removesgray/300
andgray/400
.Any chance to re-add the
gray/300
andgray/400
variations back to Odyssey?The text was updated successfully, but these errors were encountered: