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
LESS is more #9023
LESS is more #9023
Conversation
Codecov Report
@@ Coverage Diff @@
## master #9023 +/- ##
==========================================
+ Coverage 59.15% 59.45% +0.29%
==========================================
Files 367 369 +2
Lines 11686 11747 +61
Branches 2866 2888 +22
==========================================
+ Hits 6913 6984 +71
+ Misses 4594 4584 -10
Partials 179 179
Continue to review full report at Codecov.
|
LGTM, but prob needs to be tested. This definitely makes things easier to read... |
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.
A few comments, but otherwise seems legit. could you add a bunch of before and after screenshots to your test plan to confirm that this works. alternatively, you could attach a diff on the processed CSS to confirm it's all correct
|
||
div.tablePopover:hover { | ||
opacity: 1 !important; | ||
&:hover { |
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.
this is a styling thing, but personally i prefer a new line between normal styles and the &:foo {
line. I think there's a way to lint for that, if so maybe you could add that rule in another PR. if not, maybe we could start standardizing that here if you agree?
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.
I prefer that too, but glad you caught ones I missed. I'll look for a linting rule.
@@ -28,7 +28,6 @@ | |||
|
|||
.dashboard--editing { | |||
.grid-column:after { | |||
border: 1px solid transparent; |
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.
lol, what was this?
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.
There are a bunch of fairly convoluted styles around the dashed borders in the dashboard editor, which seem like they could use a simplification effort (a future PR, probably). I'll double check that this one wasn't providing some useful 1px offset.
I like this idea... will do later today. |
@etr2460 I pasted a bunch of diff screenshots above. To get these, I ran the build on master, and on this branch. I then took all the resulting CSS files from each build, removed the annoying hashes from the filenames, ran prettier on them so I could get a reasonable DIFF, and then got the DIFF via github. Hopefully I didn't screw anything up in that process, but I'm feeling pretty good about it overall :D |
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.
Thanks for all the diligence in testing and ensuring the outputted CSS is correct. And double thanks for adding the lint rule!
CATEGORY
Choose one
SUMMARY
This shouldn't change anything in the processed CSS.
Now that we have LESS everywhere, this PR just goes through and takes advantage of it, tidying up various things readability/grouping
I went through and did an
npm run build
on themaster
branch and this feature branch. I compared all resulting CSS files, and screenshots of the (innocuous as far as I can see) diffs are below - it looks like things were just re-ordered a bit:(this yields the same CSS attributes without repeating the properties)