Releases: Jarzka/stylefy
Releases · Jarzka/stylefy
1.4.0
1.3.0
- use-style function now accepts HTML attributes as the second parameter. This means that there is no need to merge the return value of use-style and HTML attributes anymore. This change is backwards compatible, so merging still works as expected.
- Updated deps (Clojure, ClojureScript & Reagent)
- stylefy now uses clj-chrome-devtools for running tests
Previously, the second parameter of use-style was an options map, containing only one keyword ::stylefy/with-classes. This feature is now deprecated, but works. If you want to provide additional classes to use-style, you should use the regular HTML :class attribute.
1.2.0
1.1.0
- Inline style map does not contain stylefy's namespaced keywords anymore(these were useless, only style properties can be used)
- Inline style map handles Garden's units and colors correctly by converting them to CSS strings
- New feature: Call stylefy/tag to reset the default style of a specific tag (like body)
1.0.1
1.0.0
Now that all major CSS features are supported, it's time to release version 1.0!
- Added support for CSS feature queries (@supports). Media queries, modes and vendor prefixes inside @supports blocks are also supported. See README.md for examples.
- Added support for using vendor prefixes and modes in media queries
- Garden option {:pretty-print? false} is now supported in media queries (this change can only be seen in tests).
As always, all changes should be backwards compatible.
0.7.3
0.7.2
- Adds support for deeper sub-style nesting by introducing a new core function: sub-style. See README & examples for information.
Thanks to @lllShamanlll for this idea!
0.7.1
0.7
- Removes public reagent atoms: keyframes-in-dom? and font-faces-in-dom?. After init function was changed to add keyframes and font-faces into the DOM immediately, the values of these atoms were basically always true.
- Adds a new public API function prepare-styles. Calling this function asks stylefy to convert the styles to CSS and add them into the DOM immediately. Calling this function on :component-will-mount can be useful if a component is going to use styles with specific modes or media queries that cannot be present as inline style, and the component should not be hidden for the small period of time when the styles are prepared to be added into the DOM.
It's good to keep in mind that most of the time prepare-styles is not needed but calling use-style should be enough.