Better ordering of style rules and properties #160
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR solves the same issues as #159 and #155, and more.
It assigns all issues reported in #140.
This pr too takes priority into account by sorting the rules via the already available method, but sorting happens later (when you need it) when rules are inserted, not when they are parsed and collected.
When processing properties it does not just overwrite the properties but it unsets and adds them.
This ensures that the order is correct and the css like the one below is processed correctly too:
The specificity tests are updated to reflect the changes made with ordering the rules and properties.
It also tests all the different uses cases mentioned in #140.