-
Notifications
You must be signed in to change notification settings - Fork 365
Print non-integer number at full precision in inspect mode #2615
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
Conversation
d6655d8
to
5669090
Compare
I did a GitHub search to find out where people are using or abusing It seems that the "legit" real world usage where this proposed change may have a small impact is: https://github.com/oddbird/true/blob/cfcd111acf0c168fd2f02cfa0c2a939dd199c189/sass/data/_details.scss#L127 @mirisuzanne @jgerigmeyer I think this change would actually make the "unpredictable" slightly better, but it would require change to the logic linked above. If you need to support both sass before and after this change, it can be implemented with a feature detection with @nex3 Any thoughts? |
I'd like to hear what Miriam and Jonny have to say, but in principle I'm supportive of this. |
Yeah, this logic makes sense to me. @mirisuzanne What do you think? |
We're not using this for core functionality, and the specific level of precision is incidental to our purpose. But at some point it was common for people to be surprised when e.g. But maybe string interpolation or some other method is better for comparing what Sass will actually output? |
Yeah, string interpolation or |
sass/sass-spec#2067