Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Fix false positives for scientific notation (ex: 9e9) in unit-no-unknown
See original GitHub issueClearly describe the bug
no-unit-unknown says Unexpected unknown unit "e9" when parsing a rule like flex-shrink: 9e9
It should eat up the e9 before the unit like the spec says for number-ident
Which rule, if any, is the bug related to?
no-unit-unknown
What CSS is needed to reproduce the bug?
a {
flex: 0 9e9 auto;
width: 1e5px;
}
What stylelint configuration is needed to reproduce the bug?
{
"rules": {
"no-unit-unknown": "true"
}
}
Which version of stylelint are you using?
9.1.2
How are you running stylelint: CLI, PostCSS plugin, Node API?
yarn stylelint style.css
Does the bug relate to non-standard syntax (e.g. SCSS, Less etc.)?
No
What did you expect to happen?
No warnings to be flagged.
What actually happened (e.g. what warnings or errors did you get)?
460:10 ✖ Unexpected unknown unit "e9" unit-no-unknown
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@chearon Thanks for the report and for using the template.
I’ve not seen that notation used in CSS before. It’s fascinating to see! Anyhow, I’ve raised an issue upstream in the value parser that we use in stylelint. Let’s wait to see whether this bug will be addressed there, or whether we’ll need to accommodate it directly in stylelint.
Fixed in https://github.com/TrySound/postcss-value-parser/releases/tag/v3.3.1, need add tests and update deps