Skip to content
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

Fix linting errors in hero.css #434

Closed
vtsaplin opened this issue Jan 10, 2024 · 1 comment
Closed

Fix linting errors in hero.css #434

vtsaplin opened this issue Jan 10, 2024 · 1 comment
Assignees

Comments

@vtsaplin
Copy link
Collaborator

No description provided.

@andreibogdan
Copy link
Collaborator

solutions/blocks/hero/hero.css
  35:1  ✖  Unexpected duplicate selector "main .hero .hero-content              no-duplicate-selectors
           .breadcrumb", first used at line 27
 135:1  ✖  Unexpected duplicate selector "main .hero .hero-content", first      no-duplicate-selectors
           used at line 121
 166:1  ✖  Unexpected duplicate selector "main .hero h1", first used at line    no-duplicate-selectors
           152
 177:1  ✖  Expected selector "main .hero h2" to come before selector "main      no-descending-specificity
           .hero.black-background h2"
 178:1  ✖  Expected selector "main .hero h4" to come before selector "main      no-descending-specificity
           .hero.black-background h4"
 440:3  ✖  Unexpected duplicate selector "main .hero  h2", first used at line   no-duplicate-selectors
           431
 469:3  ✖  Unexpected duplicate selector "main .hero .hero-content", first      no-duplicate-selectors
           used at line 462
 483:3  ✖  Unexpected duplicate selector "main .hero .hero-content > div",      no-duplicate-selectors
           first used at line 418
 535:3  ✖  Unexpected duplicate selector "main .hero h2", first used at line    no-duplicate-selectors
           531
 568:3  ✖  Unexpected duplicate selector "main .hero .hero-content", first      no-duplicate-selectors
           used at line 561

@andreibogdan andreibogdan linked a pull request Jan 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants