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

c1: QA fixes | list views #548

Merged
merged 1 commit into from
Feb 13, 2024
Merged

c1: QA fixes | list views #548

merged 1 commit into from
Feb 13, 2024

Conversation

ashwin1111
Copy link
Contributor

@ashwin1111 ashwin1111 commented Feb 13, 2024

Summary by CodeRabbit

  • Style
    • Updated styling across various components for a more consistent and visually appealing interface. Changes include:
      • Removal of outdated styling rules for table elements and buttons.
      • Enhanced progress bar designs for better visual feedback.
      • Introduction of new custom properties for the Fyle theme to improve table component aesthetics, including colors and borders.

@ashwin1111
Copy link
Contributor Author

@coderabbitai review

Copy link
Contributor

coderabbitai bot commented Feb 13, 2024

Walkthrough

The updates primarily involve the removal of specific styling rules for .p-datatable elements across various components, focusing on table rows, headers, and buttons, while enhancing or retaining styles for the .p-progressbar component. Additionally, new styling properties for tables have been introduced in the Fyle theme, and general table styling rules have been added to the global styles.

Changes

Files Change Summary
.../dashboard/dashboard.component.scss (for both Intacct and QBD) Removed .p-datatable styling for rows, headers, buttons; adjusted .p-progressbar styling.
.../export-log/.../export-log.component.scss (across all export-log components) Removed styling for td, th, button within .p-datatable; modified .p-progressbar styling.
.../dashboard-accounting-error-dialog.component.scss Removed .p-datatable styling; modified .p-datepicker styling.
.../export-log-filter.component.scss, .../export-log-table.component.scss, .../generic-mapping-table.component.scss Removed styling for table cells, headers, buttons; modified dropdown trigger styling.
src/assets/themes/fyle/fdl.scss, src/styles.scss Added custom table styling properties; added global .p-datatable styling.

🐰✨
In the land of code and hue,
A rabbit hopped, making all things new.
Out with the old, in with the blue,
Tables transformed, and progress bars too.
With every hop, the changes flew,
Crafting a scene, fresh and true.
🌈🎨🐇

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit-tests for this file.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Review Status

Actionable comments generated: 18

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 9b1162d and dfb80a8.
Files selected for processing (11)
  • src/app/integrations/intacct/main/dashboard/dashboard.component.scss (1 hunks)
  • src/app/integrations/intacct/main/export-log/completed-export-log/completed-export-log.component.scss (1 hunks)
  • src/app/integrations/intacct/main/export-log/export-log.component.scss (1 hunks)
  • src/app/integrations/intacct/main/export-log/skip-export-log/skip-export-log.component.scss (1 hunks)
  • src/app/integrations/qbd/main/dashboard/dashboard.component.scss (1 hunks)
  • src/app/shared/components/dashboard/dashboard-accounting-error-dialog/dashboard-accounting-error-dialog.component.scss (1 hunks)
  • src/app/shared/components/export-log/export-log-filter/export-log-filter.component.scss (1 hunks)
  • src/app/shared/components/export-log/export-log-table/export-log-table.component.scss (1 hunks)
  • src/app/shared/components/helper/mapping/generic-mapping-table/generic-mapping-table.component.scss (1 hunks)
  • src/assets/themes/fyle/fdl.scss (1 hunks)
  • src/styles.scss (1 hunks)
Additional comments: 3
src/assets/themes/fyle/fdl.scss (1)
  • 320-326: The addition of custom properties for table styling is a positive step towards standardizing the visual theme. Ensure these properties are well-documented and align with the design system.
src/styles.scss (2)
  • 417-419: Ensure the use of tw-font-nav-link-font-weight in .p-datatable .p-datatable-thead > tr > th is consistent with the design system and that such a font weight is defined and appropriate for table headers.
  • 421-423: The styling for .p-datatable .p-datatable-tbody > tr > td uses tw-border-t and tw-border-b-0, which ensures top borders for table cells but no bottom borders. Confirm this design choice aligns with UI guidelines for table row separation.

Comment on lines 4 to 6
@apply tw-bg-bg-info-lightest;
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [2-7]

Remove the redundant nested &:hover since the styles are already scoped to the hover state of .clickable-row.

.clickable-row:hover {
    @apply tw-cursor-pointer;
-    &:hover {
      @apply tw-bg-bg-info-lightest;
-    }
}

Comment on lines 1 to 3
:host ::ng-deep .p-datepicker table td > span.p-highlight {
@apply tw-text-white tw-bg-mandatory-field-color #{!important};
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Review the necessity of #{!important} for overriding styles and ensure it's used as a last resort due to specificity issues.


📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [4-6]

Ensure #{!important} is necessary for tw-shadow-none to avoid specificity issues.


📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [7-9]

Check if tw-text-center is correctly applied without #{!important}; consistency in the use of !important should be maintained across similar styles.

Comment on lines 2 to 7
@apply tw-w-200-px tw-border-0 #{!important};
}


:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td {
@apply tw-text-sub-text-color tw-text-14-px tw-font-400 tw-py-14-px tw-px-22-px tw-border-t tw-border-b-0 tw-border-t-box-color #{!important};
}

:host ::ng-deep .p-datatable .p-datatable-thead > tr > th {
@apply tw-text-text-primary tw-text-12-px tw-font-500 tw-py-12-px tw-px-22-px tw-border tw-border-box-color tw-bg-disabled-bg-color #{!important}
}

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td > button {
@apply tw-pl-48-px #{!important};
}

:host ::ng-deep .p-progressbar {
@apply tw-h-1.5 tw-bg-progress-bar-bg #{!important};
}
Copy link
Contributor

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [12-14]

Verify the validity of tw-rounded-50; if it's a custom class, ensure it's defined elsewhere or consider using a standard Tailwind CSS class for rounded corners.


📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [15-17]

Review the necessity of #{!important} for progress bar styles to ensure they are essential for overriding default styles.

Comment on lines 12 to 14

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td {
@apply tw-text-sub-text-color tw-text-14-px tw-font-400 tw-py-14-px tw-px-22-px tw-border-t tw-border-b-0 tw-border-t-box-color #{!important};
}

:host ::ng-deep .p-datatable .p-datatable-thead > tr > th {
@apply tw-text-text-primary tw-text-12-px tw-font-500 tw-py-12-px tw-px-22-px tw-border tw-border-box-color tw-bg-disabled-bg-color #{!important}
}

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td > button {
@apply tw-pl-48-px #{!important};
}

:host ::ng-deep .selectedItem .p-dropdown-trigger {
@apply tw-hidden #{!important};
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider creating reusable classes or utilities for dropdown styles to reduce redundancy across components.

Comment on lines 10 to 15
@apply tw-w-200-px tw-border-0 #{!important};
}

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td {
@apply tw-text-sub-text-color tw-text-14-px tw-font-400 tw-py-14-px tw-px-22-px tw-border-t tw-border-b-0 tw-border-t-box-color #{!important};
}

:host ::ng-deep .p-datatable .p-datatable-thead > tr > th {
@apply tw-text-text-primary tw-text-12-px tw-font-500 tw-py-12-px tw-px-22-px tw-border tw-border-box-color tw-bg-disabled-bg-color #{!important}
}

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td > button {
@apply tw-pl-48-px #{!important};
}

:host ::ng-deep .selectedItem .p-dropdown-trigger {
@apply tw-hidden #{!important};
}
Copy link
Contributor

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [15-17]

Review the necessity of #{!important} for hiding dropdown triggers to ensure it's essential for achieving the desired styling.

Comment on lines 35 to 40
@apply tw-w-200-px tw-border-0 #{!important};
}

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td {
@apply tw-text-sub-text-color tw-text-14-px tw-font-400 tw-py-14-px tw-px-22-px tw-border-t tw-border-b-0 tw-border-t-box-color #{!important};
}

:host ::ng-deep .p-datatable .p-datatable-thead > tr > th {
@apply tw-text-text-primary tw-text-12-px tw-font-500 tw-py-12-px tw-px-22-px tw-border tw-border-box-color tw-bg-disabled-bg-color #{!important}
}

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td > button {
@apply tw-pl-48-px #{!important};
}

:host ::ng-deep .p-progressbar {
@apply tw-h-1.5 tw-bg-progress-bar-bg #{!important};
}
Copy link
Contributor

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [1-3]

Ensure the custom search field styles are consistent with the application's design system and consider using utility classes where possible.


📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [4-6]

Review the color grey for the search icon; ensure it aligns with the application's color palette or consider using a variable for maintainability.

Comment on lines 29 to 34
@apply tw-w-200-px tw-border-0 #{!important};
}

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td {
@apply tw-text-sub-text-color tw-text-14-px tw-font-400 tw-py-14-px tw-px-22-px tw-border-t tw-border-b-0 tw-border-t-box-color #{!important};
}

:host ::ng-deep .p-datatable .p-datatable-thead > tr > th {
@apply tw-text-text-primary tw-text-12-px tw-font-500 tw-py-12-px tw-px-22-px tw-border tw-border-box-color tw-bg-disabled-bg-color #{!important}
}

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td > button {
@apply tw-pl-48-px #{!important};
}

:host ::ng-deep .p-progressbar {
@apply tw-h-1.5 tw-bg-progress-bar-bg #{!important};
}
Copy link
Contributor

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [1-3]

Ensure the custom search field styles are consistent with the application's design system and consider using utility classes where possible.


📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [4-6]

Review the color for the search icon; ensure it aligns with the application's color palette or consider using a variable for maintainability.

Comment on lines 29 to 34
@apply tw-w-200-px tw-border-0 #{!important};
}

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td {
@apply tw-text-sub-text-color tw-text-14-px tw-font-400 tw-py-14-px tw-px-22-px tw-border-t tw-border-b-0 tw-border-t-box-color #{!important};
}

:host ::ng-deep .p-datatable .p-datatable-thead > tr > th {
@apply tw-text-text-primary tw-text-12-px tw-font-500 tw-py-12-px tw-px-22-px tw-border tw-border-box-color tw-bg-disabled-bg-color #{!important}
}

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td > button {
@apply tw-pl-48-px #{!important};
}

:host ::ng-deep .p-progressbar {
@apply tw-h-1.5 tw-bg-progress-bar-bg #{!important};
}
Copy link
Contributor

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [1-3]

Ensure the custom search field styles are consistent with the application's design system and consider using utility classes where possible.


📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [4-6]

Review the color for the search icon; ensure it aligns with the application's color palette or consider using a variable for maintainability.

Comment on lines 66 to 68
:host ::ng-deep .tooltip-return {
@apply tw-mt-6-px tw-px-4-px tw-py-4-px tw-text-9-px tw-rounded-md tw-bg-placeholder #{!important}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [4-6]

Consider using utility classes for dropdown widths to ensure consistency across the application.


📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [7-9]

Review the necessity of #{!important} for disabled button text colors to ensure it's essential for achieving the desired styling.

Comment on lines 47 to 52
@apply tw-w-200-px tw-border-0 #{!important};
}

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td {
@apply tw-text-sub-text-color tw-text-14-px tw-font-400 tw-py-14-px tw-px-22-px tw-border-t tw-border-b-0 tw-border-t-box-color #{!important};
}

:host ::ng-deep .p-datatable .p-datatable-thead > tr > th {
@apply tw-text-text-primary tw-text-12-px tw-font-500 tw-py-12-px tw-px-22-px tw-border tw-border-box-color tw-bg-disabled-bg-color #{!important}
}

:host ::ng-deep .p-datatable .p-datatable-tbody > tr > td > button {
@apply tw-pl-48-px #{!important};
}

:host ::ng-deep .p-progressbar {
@apply tw-h-1.5 tw-bg-progress-bar-bg #{!important};
}
Copy link
Contributor

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [8-10]

Consider creating reusable classes or utilities for container styles to reduce redundancy across components.


📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [11-13]

Review the necessity of #{!important} for progress bar styles to ensure they are essential for overriding default styles.

@ashwin1111 ashwin1111 merged commit e3e5a58 into c1-qa-multiselect Feb 13, 2024
1 check passed
ashwin1111 added a commit that referenced this pull request Feb 14, 2024
* C1: QA Fixes - 4 | Multiselect

* fix bg

* c1: QA Fixes - Toggle (#538)

* C1 qa toast (#540)

* c1: QA Fixes - Toggle

* c1: Toast

* c1: QA fixes | Chips (#542)

* fix travelperk btn

* c1: QA fixes | list views (#548)

* C1 qa borders (#549)

* c1: QA fixes | list views

* c1: QA fixes - Border
ashwin1111 added a commit that referenced this pull request Feb 14, 2024
* C1: QA Fixes - 4 | Multiselect

* fix bg

* c1: QA Fixes - Toggle (#538)

* C1 qa toast (#540)

* c1: QA Fixes - Toggle

* c1: Toast

* c1: QA fixes | Chips (#542)

* fix travelperk btn

* c1: QA fixes | list views

* c1: QA fixes - Border

* c1: QA fixes | list views (#548)

* C1 qa borders (#549)

* c1: QA fixes | list views

* c1: QA fixes - Border

* c1: QA fixes - Calendar

* fix search

* comment out stuffs

* fix icon

* few more
ashwin1111 added a commit that referenced this pull request Feb 14, 2024
…ps | LV | Border (#531)

* C1: QA Fixes - 3

* fix lint

* other fixes

* dropdown

* dropdown with search

* fix lint

* C1 dropdown qa fix (#544)

white labeling gC1

* C1 qa multiselect | toggle | bg | toast | chips | lv | border (#536)

* C1: QA Fixes - 4 | Multiselect

* fix bg

* c1: QA Fixes - Toggle (#538)

* C1 qa toast (#540)

* c1: QA Fixes - Toggle

* c1: Toast

* c1: QA fixes | Chips (#542)

* fix travelperk btn

* c1: QA fixes | list views (#548)

* C1 qa borders (#549)

* c1: QA fixes | list views

* c1: QA fixes - Border

* c1: QA fixes - Calendar (#551)

* C1: QA Fixes - 4 | Multiselect

* fix bg

* c1: QA Fixes - Toggle (#538)

* C1 qa toast (#540)

* c1: QA Fixes - Toggle

* c1: Toast

* c1: QA fixes | Chips (#542)

* fix travelperk btn

* c1: QA fixes | list views

* c1: QA fixes - Border

* c1: QA fixes | list views (#548)

* C1 qa borders (#549)

* c1: QA fixes | list views

* c1: QA fixes - Border

* c1: QA fixes - Calendar

* fix search

* comment out stuffs

* fix icon

* few more

* fix qbd btn

* fix mapping card

* fix bamboo

* intacct search, calendar

---------

Co-authored-by: Dhaarani <[email protected]>
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.

1 participant