New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump postcss-values-replace #941
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
/cc @anikethsaha
8004607
to
29936e6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question.
And also fix the linting issue
if (u[0] === '.') { | ||
u = u.slice(1); | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why removing the leading .
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my thought is that it is not the part of unit
but the value
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for input like https://github.com/TrySound/postcss-value-parser/blob/master/test/unit.js#L10, there would be still number (length) in the unit.
I wonder whether this should be fixed in postcss-value-parser
as .3rem
or 3rem
is even a value unit or not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is not good idea
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SkReD can you undo this change and we can submit a issue in the parser repo as this should be handled by the parser not by the minifier
29936e6
to
92c434d
Compare
if (u[0] === '.') { | ||
u = u.slice(1); | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for input like https://github.com/TrySound/postcss-value-parser/blob/master/test/unit.js#L10, there would be still number (length) in the unit.
I wonder whether this should be fixed in postcss-value-parser
as .3rem
or 3rem
is even a value unit or not.
Codecov Report
@@ Coverage Diff @@
## master #941 +/- ##
=======================================
Coverage 97.51% 97.51%
=======================================
Files 120 120
Lines 3499 3501 +2
Branches 1057 1058 +1
=======================================
+ Hits 3412 3414 +2
Misses 80 80
Partials 7 7
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please add a test case mentioned here #958
5d98f96
to
5ad05d2
Compare
|
Fixed in 5.0.0. I've added the commit with the test case to #1059 |
Closes #909