Skip to content

Warnings and Code smells #73

@Ocean15

Description

@Ocean15

Hello there!

I get several deprecation warnings from sass with your theme-base:

Deprecation Warning: Sass's behavior for declarations that appear after nested
rules will be changing to match the behavior specified by CSS in an upcoming
version. To keep the existing behavior, move the declaration above the nested
rule. To opt into the new behavior, wrap the declaration in `& {}`.

More info: https://sass-lang.com/d/mixed-decls

    ┌──> src\assets\theme-base\components\data\_carousel.scss
6   │               margin: $inlineSpacing;
    │               ^^^^^^^^^^^^^^^^^^^^^^ declaration
    ╵
    ┌──> src\assets\theme-base\_mixins.scss
226 │ ┌     &:focus-visible {
227 │ │         @include focused();
228 │ │     }
    │ └─── nested rule
    ╵
    src\assets\theme-base\components\data\_carousel.scss 6:13  @import
    src\assets\theme-base\_components.scss 42:13               @import
    src\assets\themes\indigoy\theme.scss 3:9                   root stylesheet

Deprecation Warning: Sass's behavior for declarations that appear after nested
rules will be changing to match the behavior specified by CSS in an upcoming
version. To keep the existing behavior, move the declaration above the nested
rule. To opt into the new behavior, wrap the declaration in `& {}`.

More info: https://sass-lang.com/d/mixed-decls

    ┌──> src\assets\theme-base\components\data\_treetable.scss
254 │                       margin-right: $inlineSpacing;
    │                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ declaration
    ╵
    ┌──> src\assets\theme-base\_mixins.scss
226 │ ┌     &:focus-visible {
227 │ │         @include focused();
228 │ │     }
    │ └─── nested rule
    ╵
    src\assets\theme-base\components\data\_treetable.scss 254:21  @import
    src\assets\theme-base\_components.scss 52:13                  @import
    src\assets\themes\indigoy\theme.scss 3:9                      root stylesheet

Deprecation Warning: Sass's behavior for declarations that appear after nested
rules will be changing to match the behavior specified by CSS in an upcoming
version. To keep the existing behavior, move the declaration above the nested
rule. To opt into the new behavior, wrap the declaration in `& {}`.

More info: https://sass-lang.com/d/mixed-decls

    ┌──> src\assets\theme-base\components\overlay\_dialog.scss
21  │               margin-right: $inlineSpacing;
    │               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ declaration
    ╵
    ┌──> src\assets\theme-base\_mixins.scss
226 │ ┌     &:focus-visible {
227 │ │         @include focused();
228 │ │     }
    │ └─── nested rule
    ╵
    src\assets\theme-base\components\overlay\_dialog.scss 21:13  @import
    src\assets\theme-base\_components.scss 69:13                 @import
    src\assets\themes\indigoy\theme.scss 3:9                     root stylesheet

I also get a lot of "Unexpected duplicate selector" warnings from my sonarqube because of the theme-base. I can ignore the folder from being scanned but there are some very strange code fragments in your library you should check. For example: /theme-base/components/input/_checkbox.scss line 40-60 and 62-82 contain the exact same code.

Greetings
Ocean

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions