This Pull Request is taking longer than usual (4 days) to be finished.
🎉 Congratulations!
This Pull Request does not add any new issues to your codebase.
-
Incorrect list-item indent: add 1 space
README.md 2. Run `mix test`
3. Run `iex -S mix phx.server` and visit [http://localhost:4000/](http://localhost:4000/)
After this succeeds you should be good to go!
-
Incorrect list-item indent: add 1 space
README.md 1. Run `mix setup` to install dependencies, create and seed database etc
2. Run `mix test`
3. Run `iex -S mix phx.server` and visit [http://localhost:4000/](http://localhost:4000/)
-
Incorrect list-item indent: add 1 space
README.md 1. Run `mix setup` to install dependencies, create and seed database etc
2. Run `mix test`
3. Run `iex -S mix phx.server` and visit [http://localhost:4000/](http://localhost:4000/)
-
!importantshould not be used.assets/css/template/_user.scss .user-edit a {
font-weight: 400 !important;
} -
Selector should have depth of applicability no greater than 4, but was 5.
Nested selectors are highly coupled to the DOM structure, they will produce less efficient selectors and they compromises the readability of your code although it reduces the duplication of parent selectors. It is recommended to follow the inception rule in such scenarios.
You can reduce this nesting by introducing new selectors targeting the nested elements instead of relying in their parent / child dependency.
assets/css/template/_stats.scss &.no-wrap {
display: inline-block;
} -
Selector should have depth of applicability no greater than 4, but was 5.
Nested selectors are highly coupled to the DOM structure, they will produce less efficient selectors and they compromises the readability of your code although it reduces the duplication of parent selectors. It is recommended to follow the inception rule in such scenarios.
You can reduce this nesting by introducing new selectors targeting the nested elements instead of relying in their parent / child dependency.
assets/css/template/_stats.scss @media (min-width: 576px) {
&.wrap {
display: none;
} -
Selector should have depth of applicability no greater than 4, but was 5.
Nested selectors are highly coupled to the DOM structure, they will produce less efficient selectors and they compromises the readability of your code although it reduces the duplication of parent selectors. It is recommended to follow the inception rule in such scenarios.
You can reduce this nesting by introducing new selectors targeting the nested elements instead of relying in their parent / child dependency.
assets/css/template/_stats.scss &.no-wrap {
display: none;
} -
Selector should have depth of applicability no greater than 4, but was 5.
Nested selectors are highly coupled to the DOM structure, they will produce less efficient selectors and they compromises the readability of your code although it reduces the duplication of parent selectors. It is recommended to follow the inception rule in such scenarios.
You can reduce this nesting by introducing new selectors targeting the nested elements instead of relying in their parent / child dependency.
assets/css/template/_stats.scss @media (max-width: 575px) {
&.wrap {
display: inline-block;
} -
Selector should have depth of applicability no greater than 4, but was 5.
Nested selectors are highly coupled to the DOM structure, they will produce less efficient selectors and they compromises the readability of your code although it reduces the duplication of parent selectors. It is recommended to follow the inception rule in such scenarios.
You can reduce this nesting by introducing new selectors targeting the nested elements instead of relying in their parent / child dependency.
assets/css/template/_stats.scss .count-info {
font-weight: bold;
white-space: nowrap;
-
Each selector in a comma sequence should be on its own single line
assets/css/template/_sponsors.scss .dashbit .image, .travis .image {
margin-bottom: 10px;
}