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
Refactor/2318/migrate attribute type selector #2519
Conversation
Tests are still missing. ref: #2318
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.
ref: 2318
Thx for the catch! Fixed with f9f2419 |
visualization/app/codeCharta/ui/attributeTypeSelector/attributeTypeSelector.component.scss
Outdated
Show resolved
Hide resolved
visualization/app/codeCharta/ui/attributeTypeSelector/attributeTypeSelector.component.scss
Show resolved
Hide resolved
left: 8px; | ||
} | ||
&:hover { | ||
background-color: rgb(200, 200, 200); |
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.
We used #c8c8c8 before, for most hovers. But this is a personal preference to use hex codes over rgb
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.
done
</div> | ||
|
||
<mat-menu #menu> | ||
<div class="menu-header" mat-menu-item disabled>Set global aggregation for rloc</div> |
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.
Personal preference, but i think a span or any other generic text element would be cleaner than just writing the text straight into a div, since we could in theory have spans standardized across the project but not generic text in divs.
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.
The advantage of this standard isn't clear to me. Anyway, lets not spend time in something which we might do, while "just" migrating to Angular, which is already a very very huge task :P
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.
Text just in a div has no semantic meaning for text, its used for layout, while span is used to style texts. If that makes more sense
} | ||
} | ||
|
||
.mat-menu-item { |
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.
.mat-menu-item is a child of .mat-menu-content and could be in the same paranthesis level as .menu-header above
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.
done
} | ||
|
||
.mat-menu-item { | ||
font-size: 16px; |
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.
Generally id preffer pt over px, when working with fonts
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.
Generally I agree. But as we mix it up everywhere and have no concept for it so far, I don't want to invest any time into it while migrating.
…eTypeSelector.component.scss Co-authored-by: Christian-Eberhard <42114276+Christian-Eberhard@users.noreply.github.com>
[CodeCharta Analysis] Kudos, SonarCloud Quality Gate passed! |
[CodeCharta Visualization] Kudos, SonarCloud Quality Gate passed! |
"edges"
as it was unused.font-size: 15px
->font-size: 16px
as it looks better to me. I think not worth any discussion or mention in changelog.