-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
Replace Sass division with multiplication and custom divide() function #34571
Conversation
@mdo it seems on v4-dev we are using rfs 8.x. I'll try to see if I can cut a new 8.x release with the Dart Sass fix and then push here any patches. That being said, I recall we still had some issues with the rounding on main. Are those sorted? If not, I'd wait until we fix everything before backporting. |
I think everything has been sorted? We may have lost 1-2 decimals but I haven't heard any rounding bugs since we shipped the last release. |
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.
💪👌
@mdo I created an upstream branch https://github.com/twbs/rfs/commits/v8.x. Feel free to backport the divide fix with a PR. Just keep in mind that in the upstream 8.x branch we don't test dart Sass. |
Fixes #34353. Co-Authored-By: Slaven Tomac <[email protected]>
Pulled the latest in from that branch, thanks @XhmikosR! Just rebased and force pushed. Should be good to go. |
@mdo Is it ok using I think it's considered as a "good practice" and also we're used to see float numbers with a |
really sorry to nag/comment, is the only thing left on this fix to convert |
Stylistically, we don't include leading |
Hi, just wondering if this will move ahead, it's been getting stale, and it seems like an important thing. I'll reference the above Merge request comment (from petrsiegl):
|
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.
LGTM, what would be missing now?
@ffoodd This is NOT ready due to RFS,please do not approve things like that because I might then accidentally merge stuff :) |
Latest comments involving RFS felt accurate and up-to-date :D What's missing? Shouldn't we convert this to draft? |
@ffoodd the backported version doesn't have the division fix. We need an upstream patch against the https://github.com/twbs/rfs/commits/v8.x branch. |
Just to be clear — in order to get this approved twbs/rfs#398 (essentially) needs to be backported to RFS v8.x? @ffoodd are you planning to do that work or does someone else need to jump in? |
Someone needs to do the work and provide an upstream PR, because the patch cannot be cherrypicked unfortunately. |
Fixes #34353. Replaces #34386.
@XhmikosR I removed the RFS changes from that other PR for now. Want to take a stab at porting it to this branch?