Skip to main content

Migration from Other Libs

There are very similar older libraries out there:

  • react-css-themr – the original inspiration for this work
  • react-css-super-themr – an earlier attempt to maintain and enhance react-css-themr, which was not maintained by its original author for quite some time, before getting new maintainers recently.

To migrate from them to this library you should patch your code to address the following points below:

info

Prior to v2.0.0 this library had a special «compatibility mode» able to closely emulate behavior of react-css-themr / react-css-super-themr libraries. You may consider to migrate to the version v1.4.9 of this library first, using that mode (activated by setCompatibilityMode() function), and then migrate to its v2+ in the follow-up step.

react-css-themr​

These are the differences of React Themes library compared to react-css-themr:

  • Composition mode values are changed from "deeply", "softly", and false to "DEEP", "SOFT", and "SWAP".

  • Default theme priority is ADHOC_CONTEXT_DEFAULT instead of ADHOC_DEFAULT_CONTEXT, also the actual priority mode values have changed from adhoc-context-default, and adhoc-default-context.

  • mapThemrProps option of themed component decorator is replaced by mapThemeProps.

  • composeTheme option of themed component decorator is replaced by two separate options: composeAdhocTheme, and composeContextTheme.

  • Themes require specifity wrappers (however, any theming that used to work fine without them, should keep on working fine, although correct deep theme merging won't work in complex scenarios).

react-css-super-themr​

  • Composition mode values are changed from "deeply", "softly", and false to "DEEP", "SOFT", and "SWAP".

  • Default theme priority is ADHOC_CONTEXT_DEFAULT instead of ADHOC_DEFAULT_CONTEXT, also the actual priority mode values have changed from adhoc-context-default, and adhoc-default-context.

  • mapThemrProps option of themed component decorator is replaced by mapThemeProps.

  • Themes require specifity wrappers (however, any theming that used to work fine without them, should keep on working fine, although correct deep theme merging won't work in complex scenarios).