-
Notifications
You must be signed in to change notification settings - Fork 269
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
[ACS-6140] - Remove references to internal Angular Material CSS classes #9271
[ACS-6140] - Remove references to internal Angular Material CSS classes #9271
Conversation
067c329
to
8000e61
Compare
...arch/components/search-chip-autocomplete-input/search-chip-autocomplete-input.component.scss
Show resolved
Hide resolved
...-services/src/lib/search/components/search-filter-tabbed/search-filter-tabbed.component.scss
Show resolved
Hide resolved
&-datatable-selected.mat-icon { | ||
height: 100%; | ||
width: 100%; | ||
margin-left: -2px; |
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.
727a9e4
to
e0733e0
Compare
lib/process-services-cloud/src/lib/task/start-task/components/start-task-cloud.component.scss
Outdated
Show resolved
Hide resolved
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.
looks great, please see comments
(selectedIndexChange)="onTabSelectionChange($event)" | ||
[class.adf-content-node-selector-headless-tabs]="!canPerformLocalUpload()"> | ||
<mat-tab label="{{ 'NODE_SELECTOR.REPOSITORY' | translate }}"> | ||
<adf-content-node-selector-panel |
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.
What's happening here? it doesn't seem a style refactoring
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.
Yes, it's refactor of angular materials component usage. In my opinion current usage was not correct. It created a mat-tab-group, which in some cases showed only one tab and was hiding all the styling from mat-tab components. In other case it had 2 tabs and displayed everything normally. It requrired a lot of css manipulation. I think it's easier and more clear to separate those 2 situations: if required show everything in mat-tab component, else show it normally. Thanks to that, there is no need in css manipulation and I could delete some parts of scss files with mat- names.
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.
I understand but as this is already a huge PR wouldn't it be possible to target this work on a separated PR?
@@ -38,72 +38,64 @@ | |||
|
|||
<mat-menu #menu="matMenu" id="user-profile-lists" [xPosition]="menuPositionX" [yPosition]="menuPositionY" | |||
[overlapTrigger]="false" class="adf-userinfo-menu"> | |||
<mat-tab-group id="tab-group-env" (click)="stopClosing($event)" selectedIndex="0" role="menuitem" |
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.
Also here, isn't this a rework of the user-info for content?
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.
same situation
...arch/components/search-chip-autocomplete-input/search-chip-autocomplete-input.component.scss
Show resolved
Hide resolved
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.
I've added some comments please have a look
@@ -19,7 +19,7 @@ | |||
</button> | |||
|
|||
<mat-menu #filter="matMenu" | |||
class="adf-filter-menu" | |||
class="adf-filter-menu adf-search-filter-menu" |
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.
Wouldn't it be better have just a single style for this one?
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.
Yes, it would, but the css specificity from angular material, makes me do this that way as they do the same thing sometimes. I couldn't have found a better solution for that
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 can incorporate the style we need to add in the normal style flow, having multiple styles is something we avoided as it created a lot of confusion long ago, if this component need that style please add it to the relative one
@@ -1,11 +1,11 @@ | |||
<mat-tree class="adf-tree-view-main" [dataSource]="dataSource" | |||
[treeControl]="treeControl" *ngIf="nodeId; else missingNodeId"> | |||
<mat-tree-node class="adf-tree-view-node" | |||
<mat-tree-node class="adf-tree-view adf-tree-view-node" |
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.
as above wouldn't it be easier to have a single style for this?
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.
same situation
*matTreeNodeDef="let treeNode" id="{{treeNode.name + '-tree-node'}}" | ||
matTreeNodePadding [matTreeNodePaddingIndent]="15"> | ||
{{treeNode.name}} | ||
</mat-tree-node> | ||
<mat-tree-node class="adf-tree-view-node" | ||
<mat-tree-node class="adf-tree-view adf-tree-view-node" |
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.
here too
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.
same situation
<mat-icon mat-list-icon>insert_drive_file</mat-icon> | ||
<p mat-line class="adf-version-list-item-name" [id]="'adf-version-list-item-name-' + version.entry.id" >{{version.entry.name}}</p> | ||
<p mat-line class="adf-version-list-item-line adf-version-list-item-name" [id]="'adf-version-list-item-name-' + version.entry.id" >{{version.entry.name}}</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.
as 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.
same situation
<span *ngIf="showName" id="adf-userinfo-identity-name-display" class="adf-userinfo-name"> | ||
{{identityUser | fullName}} | ||
</span> | ||
<button mat-button [matMenuTriggerFor]="menu" class="adf-userinfo-menu_button" | ||
<button mat-button [matMenuTriggerFor]="menu" class="adf-userinfo-menu_button adf-identity-userinfo-button" |
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.
multiple styles here as well
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.
same situation
lib/process-services-cloud/src/lib/task/start-task/components/start-task-cloud.component.scss
Outdated
Show resolved
Hide resolved
.../lib/task/task-filters/components/task-filter-dialog/task-filter-dialog-cloud.component.scss
Outdated
Show resolved
Hide resolved
e0733e0
to
d153c38
Compare
d153c38
to
c510cd7
Compare
c510cd7
to
bea035c
Compare
bea035c
to
46cca6b
Compare
46cca6b
to
8116b47
Compare
Quality Gate passedIssues Measures |
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
What is the new behaviour?
All internal Angular Material CSS classes are removed and replaced with our custom classes. Changes in Angular Material library with classes won't affect our app.
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: