-
Notifications
You must be signed in to change notification settings - Fork 101
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
Rule list order should be preserved after Emotion.makeDict #95
Comments
The reverse has been introduced here #23 with the rewrite of bs-css and is discussed in the issue. |
This will have to be explained very well in the changelog/release notes since this changes how rules override other rules. Meaning if you have let base = Css.([color(blue)]);
let style = Css.([color(red), ...base]); version 8 will end up with |
The fact that the previous styling was backwards is a headache, but fixing it is essential to #86 I think. |
yes, it needs to be written in release notes, but if you don't reverse the list you get exactly what you write, it's less magic |
I agree it was completely unintuitive. Overriding rules in the reverse order makes no sense and this was mainly added so that you could override rules and use the spread operator. This will not fix #86 though since you always lose duplicate selectors using this method. I’m working on a PR for new |
On current master, the order of properties is backwards from how it ultimately ends up in CSS.
Presumably this is because here we reverse the rule list before passing it into the JS object creator.
I noticed this because of the interaction between properties like border and border left. Order matters in this case.
Changing the order to match existing CSS was part of #92, but was stripped out with the merge changes I'd added. I've been using my own fork because of this, but I'd like to have it patched upstream. What better than a major release?
The text was updated successfully, but these errors were encountered: