Support for every property #144
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So far RFS could be used to rescale font sizes, but with the new implementation other properties can also make use of rfs' rescaling mechanism.
Features
Changes
!important
rules:@include rfs(1rem !important)
instead of@include rfs(1rem, true)
max-width
media queries if neededpx
-values should always have a unit now. Inv8
, RFS assumed every unitless value was set inpx
(eg.@include rfs(32)
), but since we can now pass numbers too (eg.@include rfs(1 1 30rem, flex)
, this behaviour is changed.PostCSS implementation change
responsive-font-size
property changed torfs()
function (see Alternative PostCSS implementation #116)Drops
responsive-font-size
mixinsMeta
/test/expected/main.css
postcss-value-parser
dependency added to parse values in PostCSS plugin.Demos
// $enable-rfs: false;
to see the difference)TODOs
postcss-value-parser
to parse values to prevent issues with nested functions (likecalc()
orrgba()
)rfsValue
andrfsFluidValue
functions so that they can be used by other js plugins or node applicationsFixes #116
Fixes #139
Fixes #154