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

[ACS-6211] Fixed UI alignment issues in create rules screen (CardView and child components) #9101

Merged

Conversation

swapnil-verma-gl
Copy link
Contributor

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation
  • Other... Please describe:
    Minor UI and styling adjustments

What is the current behaviour? (You can also link to an open issue here)
UI for the cardView Component when viewed inside CreateRules section in ACA had alignment issues

What is the new behaviour?
Adjusted the UI/styling slightly, to fix alignment issues

Does this PR introduce a breaking change? (check one with "x")

  • Yes
  • No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:
This PR links to this comment on this PR

@@ -22,7 +22,14 @@ import { BaseCardView } from '../base-card-view';

@Component({
selector: 'adf-card-view-boolitem',
templateUrl: './card-view-boolitem.component.html'
templateUrl: './card-view-boolitem.component.html',
styles: [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't it better and more clear to move it to .scss file?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only reason I added it here is because it's only a single class, and the scss file did not exist. However, if needed, I can create a new file and add the styling to that instead.

@@ -11,7 +7,8 @@
data-automation-class="read-only-value">{{ (property.displayValue | async) | translate }}
</div>
<div *ngIf="isEditable()">
<mat-form-field class="adf-select-item-padding-editable adf-property-value">
<mat-form-field class="adf-property-value" appearance="standard">
<mat-label>{{ property.label }}</mat-label>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't it the breaking change for some use cases? Right now the label will only be displayed when the field is editable

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-added the label only for non-editable mode. For editable mode, we are still using the mat-label introduced in this PR. The reason I went for this approach is to maintain consistency of this component with the rest of the applications. I've also added corresponding unit tests for both the labels

@swapnil-verma-gl swapnil-verma-gl force-pushed the dev-swapnil-acs-6211-card-view-item-ui-issue branch from 703c444 to 9999720 Compare December 5, 2023 07:31
@swapnil-verma-gl swapnil-verma-gl force-pushed the dev-swapnil-acs-6211-card-view-item-ui-issue branch from 9999720 to bedfbf1 Compare December 26, 2023 06:02
Copy link

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@swapnil-verma-gl swapnil-verma-gl merged commit 5054679 into develop Jan 3, 2024
33 checks passed
@swapnil-verma-gl swapnil-verma-gl deleted the dev-swapnil-acs-6211-card-view-item-ui-issue branch January 3, 2024 06:49
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 this pull request may close these issues.

4 participants