-
-
Notifications
You must be signed in to change notification settings - Fork 777
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
Updated scss to only target h2 on privacy policy page #4945
Updated scss to only target h2 on privacy policy page #4945
Conversation
Want to review this pull request? Take a look at this documentation for a step by step guide! From your project repository, check out a new branch and test the changes.
|
ETA: July 17 EOD |
ETA: July 17 EOD |
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.
Branches look good, code changes seem in line with the issue that needed to be addressed.
I see that 311 page and the join us page the margin at the top for each card is reduced which is the expected outcome.
Good job and thank you for taking up this issue for hackforla.
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 taking this issue @angelenelm.
Branch name looks good, and I checked using docker to confirm that there aren't any breaking changes as a result of applying a class to affect only the h2 elements in privacy policy page.
@roslynwythe @t-will-gillis -- tagging you guys as Roslyn suggested during Sunday meeting regarding one of the linter not passing.
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.
Thank you for taking up this issue, everything works perfectly on my end no issue with the linter.
When I run it on my own repo the test case passes, but the current test keeps failing, how weird |
I wonder if you can refactor to
I'm also not the best in SCSS, haven't really used it much. |
@t-will-gillis It pass locally on my side, but still seems like it is failing here, you can figure it out and then merge. |
@t-will-gillis if there is still an issue I was thinking of trying to add this rule set in the .stylelintrc.json file I mean, try to add this to the .stylelintrc.json file. Obviously, add the rest of the other rules already on the stylelintrc.json file as well, but I don't know if this will work cause says we need to npm install dev dependency, but it might work without it. { |
2d477f6
After some research I saw that the error could be thrown due to the comment syntax starting on line 60. Stylelint doesn't support SCSS but can with this config. Let me know what the best course of action should be :) |
I saw the check is failing at line 30, which isn't a section I touched so I'm not sure what's going on |
try it, try to modify the .stylelintrc.json file to extend the package you are referring to see if it works without npm install, I'm still kind of confused about npm install and package.json for this whole project cause there isn't one in the root. |
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.
hi @angelenelm Thanks for your patience! Your issue looks great as the previous reviewers have indicated.
The 'fail' that is happening with the Lint SCSS is likely caused by some conflicts that occurred when the we updated github/super-linter
to v5.0.0 per the Dependabot. Some other PRs/ issues are being flagged with the same 'fail' message, so this is not unique to yours.
Would you please revert the changes to .stylelintrc.json
? After that we can merge your PR. We will open a new issue to address the Lint SCSS.
Thank you!
@t-will-gillis Thanks so much for the explanation! The changes to that file have been removed. |
Fixes #4864
What changes did you make?
h2
selector on lines 52-54 (within@media #{$bp-desktop-up}
) to targeth2
s in.content-section--privacy-policy
class, which corresponds toh2
s in the Privacy Policy cardWhy did you make the changes (we will use this info to test)?
h2
styling should only be targeting theh2
s on the Privacy Policy page, but they are targeting everyh2
throughout the website. These changes are to specifically style theh2
s on the Privacy Policy page.Screenshots
Visuals before changes are applied
Join Us page:
Privacy Policy page:
Visuals after changes are applied
Join Us page (headers here are no longer being affected):
Privacy Policy page (headers here are still affected):