Skip to content

Replace old icon with font-awesome icons #2770

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

Merged
merged 18 commits into from
Jan 23, 2025
Merged

Replace old icon with font-awesome icons #2770

merged 18 commits into from
Jan 23, 2025

Conversation

Sameh16
Copy link
Collaborator

@Sameh16 Sameh16 commented Jan 20, 2025

Changes proposed ✍️

Note::

The old-icon component is still used for the git-repository icon ==> as it does not exist in FA lib

Summary by CodeRabbit

Release Notes

  • Icons

    • Updated icon components across the application for improved visual consistency
    • Replaced legacy icon components with new LfIcon component
    • Modernized icon names and styles
    • Added support for icon types (regular, solid, brands)
  • Visual Enhancements

    • Refreshed icons in various components including dropdowns, buttons, and status indicators
    • Standardized icon representation across different modules
    • Improved icon clarity and design
  • Compatibility

    • Maintained existing functionality while updating icon implementation
    • Seamless transition to new icon system without disrupting user experience

…Discourse, and Jira integration views

Signed-off-by: Sameh16 <[email protected]>
@Sameh16 Sameh16 self-assigned this Jan 20, 2025
Copy link

coderabbitai bot commented Jan 20, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This pull request introduces a comprehensive update to icon components across the frontend codebase. The changes involve replacing old icon components (lf-icon-old) with a new, more standardized lf-icon component. This transition spans multiple modules and components, focusing on updating icon names, introducing icon types, and ensuring visual consistency. The modifications are primarily cosmetic, maintaining the existing functionality while enhancing the visual representation of icons throughout the application.

Changes

File Path Change Summary
frontend/src/config/integrations/* Updated icon components in various integration configuration files
frontend/src/modules/admin/modules/integration/* Replaced icon components in integration status and configuration components
frontend/src/modules/contributor/components/* Comprehensive icon updates across contributor-related components
frontend/src/modules/data-quality/components/* Updated icon components in data quality modules
frontend/src/modules/organization/components/* Extensive icon component replacements in organization-related components
frontend/src/integrations/*/config.js Updated icon and icon type properties in integration configurations

Possibly related PRs

Suggested reviewers

  • gaspergrom

Poem

🐰 Hop, hop, icons take flight!
From old to new, a visual delight
Components dance with fresh design
Icons now sparkle and brightly shine
A rabbit's code update, oh so bright! 🌟


🪧 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>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • 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/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@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.

Actionable comments posted: 13

🧹 Nitpick comments (9)
frontend/src/modules/contributor/components/details/overview/contributor-details-projects.vue (1)

93-93: Consider consistent Font Awesome style usage.

While the icon choices are semantically appropriate, the fa-sharp style is used inconsistently across the dropdown menu icons. Consider either:

  1. Applying fa-sharp to all icons for consistency
  2. Removing fa-sharp if the visual difference is not significant
-                    <lf-icon name="ellipsis-vertical" type="regular" />
+                    <lf-icon name="ellipsis-vertical fa-sharp" type="regular" />
-                  <lf-icon name="eye" />View activity
+                  <lf-icon name="eye fa-sharp" />View activity

Also applies to: 97-97, 100-100, 111-111

frontend/src/modules/organization/components/lf-member/organization-lf-member-tag.vue (1)

4-4: Consider using size prop instead of class binding for icon size.

While the icon migration looks good, consider using the :size prop instead of iconFontSize class binding for consistency with other components in the codebase.

-      <lf-icon name="circle-bookmark" :class="iconFontSize" />
+      <lf-icon name="circle-bookmark" :size="16" />

Also applies to: 12-12

frontend/src/shared/modules/identities/components/verified-identity-badge.vue (1)

Line range hint 1-4: Consider creating an issue to track the tooltip z-index problem.

The TODO comment indicates an existing z-index issue with the lf-tooltip component that should be tracked and resolved.

Would you like me to create an issue to track the tooltip z-index problem?

frontend/src/modules/organization/components/organization-selection-dropdown.vue (1)

4-4: Add type specification for consistency.

While the icon replacement is correct, the type property should be specified for consistency with other icon usages.

-      <lf-icon name="house-building" class="text-gray-200 account-icon text-center h-16 flex items-center" />
+      <lf-icon name="house-building" type="regular" class="text-gray-200 account-icon text-center h-16 flex items-center" />
frontend/src/config/integrations/github/components/settings/github-settings-org-item.vue (2)

9-9: Add type property to the icon component.

For consistency with other icons in the codebase, specify the icon type (regular/solid).

-              <lf-icon name="house-building" :size="12" class="text-gray-400" />
+              <lf-icon name="house-building" type="regular" :size="12" class="text-gray-400" />

20-22: Add type property to the sync status icon.

The sync status icon should specify its type for consistent styling.

-          <lf-icon name="arrows-rotate" />
+          <lf-icon name="arrows-rotate" type="regular" />
frontend/src/modules/organization/components/details/email/organization-details-email-item.vue (1)

54-54: Standardize icon naming convention.

There's inconsistent usage of the "fa-sharp" modifier across icons. Either use it consistently for all icons or remove it.

-        <lf-icon name="pen fa-sharp" />Edit email
+        <lf-icon name="pen" type="regular" />Edit email
-        <lf-icon name="link-simple-slash" />Unmerge email
+        <lf-icon name="link-simple-slash" type="regular" />Unmerge email
-        <lf-icon name="message-exclamation" class="!text-red-500" />Report issue
+        <lf-icon name="message-exclamation" type="regular" class="!text-red-500" />Report issue
-        <lf-icon name="trash-can" />Delete email
+        <lf-icon name="trash-can" type="regular" />Delete email

Also applies to: 61-61, 71-71, 83-83

frontend/src/modules/contributor/components/details/work-history/contributor-details-work-history-item.vue (1)

15-15: Standardize icon properties across the component.

Icons should have consistent type properties and naming conventions.

-          <lf-icon name="calendar" :size="16" class="mr-1.5 text-gray-400" />
+          <lf-icon name="calendar" type="regular" :size="16" class="mr-1.5 text-gray-400" />
-            <lf-icon name="ellipsis" type="regular" />
+            <lf-icon name="ellipsis" type="regular" />
-          <lf-icon name="pen fa-sharp" />Edit work experience
+          <lf-icon name="pen" type="regular" />Edit work experience
-          <lf-icon name="message-exclamation fa-sharp" class="!text-red-500" />Report issue
+          <lf-icon name="message-exclamation" type="regular" class="!text-red-500" />Report issue
-            <lf-icon name="trash-can" />Delete work experience
+            <lf-icon name="trash-can" type="regular" />Delete work experience

Also applies to: 23-23, 28-28, 37-37, 42-42

frontend/src/modules/organization/components/details/domains/organization-details-domain-item.vue (1)

36-36: Consider adding a type attribute for the ellipsis icon.

While the icon works, consider adding type="regular" for consistency with other Font Awesome icons.

-            <lf-icon name="ellipsis" />
+            <lf-icon name="ellipsis" type="regular" />
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 280c8a9 and 00f1ad1.

📒 Files selected for processing (103)
  • frontend/src/config/integrations/confluence/components/confluence-params.vue (4 hunks)
  • frontend/src/config/integrations/devto/components/devto-connect-drawer.vue (3 hunks)
  • frontend/src/config/integrations/devto/components/devto-params.vue (4 hunks)
  • frontend/src/config/integrations/discourse/components/discourse-params.vue (3 hunks)
  • frontend/src/config/integrations/github/components/settings/github-settings-add-repository-modal.vue (1 hunks)
  • frontend/src/config/integrations/github/components/settings/github-settings-org-item.vue (2 hunks)
  • frontend/src/config/integrations/jira/components/jira-params.vue (3 hunks)
  • frontend/src/integrations/github/config.js (1 hunks)
  • frontend/src/integrations/linkedin/config.js (1 hunks)
  • frontend/src/modules/admin/modules/integration/components/integration-status.vue (1 hunks)
  • frontend/src/modules/admin/modules/integration/components/status/integration-platform-select.vue (2 hunks)
  • frontend/src/modules/admin/modules/integration/config/status/connecting.ts (1 hunks)
  • frontend/src/modules/admin/modules/integration/config/status/done.ts (1 hunks)
  • frontend/src/modules/admin/modules/integration/config/status/error.ts (1 hunks)
  • frontend/src/modules/admin/modules/integration/config/status/index.ts (1 hunks)
  • frontend/src/modules/admin/modules/integration/config/status/waiting-for-action.ts (1 hunks)
  • frontend/src/modules/admin/modules/integration/pages/integration-status.page.vue (2 hunks)
  • frontend/src/modules/admin/modules/projects/components/fragments/lf-project-count.vue (1 hunks)
  • frontend/src/modules/contributor/components/details/contributor-details-actions.vue (4 hunks)
  • frontend/src/modules/contributor/components/details/contributor-details-activities.vue (3 hunks)
  • frontend/src/modules/contributor/components/details/contributor-details-work-history.vue (1 hunks)
  • frontend/src/modules/contributor/components/details/header/contributor-details-header-profile-photo.vue (2 hunks)
  • frontend/src/modules/contributor/components/details/header/contributor-details-header-profiles.vue (4 hunks)
  • frontend/src/modules/contributor/components/details/identity/contributor-details-identity-add-dropdown.vue (3 hunks)
  • frontend/src/modules/contributor/components/details/identity/contributor-details-identity-item.vue (8 hunks)
  • frontend/src/modules/contributor/components/details/overview/contributor-details-attributes.vue (3 hunks)
  • frontend/src/modules/contributor/components/details/overview/contributor-details-community.vue (3 hunks)
  • frontend/src/modules/contributor/components/details/overview/contributor-details-projects.vue (5 hunks)
  • frontend/src/modules/contributor/components/details/overview/project/contributor-details-projects-affiliation.vue (3 hunks)
  • frontend/src/modules/contributor/components/details/overview/project/contributor-details-projects-sorting.vue (2 hunks)
  • frontend/src/modules/contributor/components/details/work-history/contributor-details-work-history-item.vue (3 hunks)
  • frontend/src/modules/contributor/components/edit/affilations/contributor-affilations-edit-item.vue (3 hunks)
  • frontend/src/modules/contributor/components/edit/affilations/contributor-affilations-edit.vue (4 hunks)
  • frontend/src/modules/contributor/components/edit/contributor-add.vue (4 hunks)
  • frontend/src/modules/contributor/components/edit/contributor-edit-profile-photo.vue (2 hunks)
  • frontend/src/modules/contributor/components/edit/identity/contributor-identity-add.vue (5 hunks)
  • frontend/src/modules/contributor/components/edit/identity/contributor-identity-edit.vue (3 hunks)
  • frontend/src/modules/contributor/components/edit/work-history/contributor-work-history-edit.vue (3 hunks)
  • frontend/src/modules/contributor/components/shared/contributor-dropdown.vue (2 hunks)
  • frontend/src/modules/contributor/components/shared/contributor-engagement-level.vue (2 hunks)
  • frontend/src/modules/contributor/components/shared/contributor-sentiment.vue (3 hunks)
  • frontend/src/modules/contributor/components/shared/contributor-syncing-activities.vue (2 hunks)
  • frontend/src/modules/contributor/components/shared/contributor-work-position.vue (2 hunks)
  • frontend/src/modules/contributor/pages/contributor-details.page.vue (3 hunks)
  • frontend/src/modules/data-quality/components/member/data-quality-member-issues.vue (2 hunks)
  • frontend/src/modules/data-quality/components/member/data-quality-member-merge-suggestions-item.vue (2 hunks)
  • frontend/src/modules/data-quality/components/member/data-quality-member-merge-suggestions.vue (2 hunks)
  • frontend/src/modules/data-quality/components/organization/data-quality-organization-merge-suggestions-item.vue (3 hunks)
  • frontend/src/modules/data-quality/components/organization/data-quality-organization-merge-suggestions.vue (2 hunks)
  • frontend/src/modules/data-quality/components/shared/data-quality-project-dropdown.vue (3 hunks)
  • frontend/src/modules/lf/layout/components/lf-menu-project-group-selection.vue (2 hunks)
  • frontend/src/modules/member/components/list/member-list-table.vue (2 hunks)
  • frontend/src/modules/member/components/member-dropdown-content.vue (10 hunks)
  • frontend/src/modules/member/components/member-unmerge-dialog.vue (3 hunks)
  • frontend/src/modules/member/components/suggestions/member-merge-suggestion-dropdown.vue (2 hunks)
  • frontend/src/modules/organization/components/details/domains/organization-details-domain-item.vue (7 hunks)
  • frontend/src/modules/organization/components/details/email/organization-details-email-item.vue (6 hunks)
  • frontend/src/modules/organization/components/details/header/organization-details-header-logo.vue (2 hunks)
  • frontend/src/modules/organization/components/details/header/organization-details-header-profiles.vue (4 hunks)
  • frontend/src/modules/organization/components/details/identity/organization-details-identity-item.vue (5 hunks)
  • frontend/src/modules/organization/components/details/organization-details-actions.vue (4 hunks)
  • frontend/src/modules/organization/components/details/organization-details-activities.vue (3 hunks)
  • frontend/src/modules/organization/components/details/organization-details-contributors.vue (5 hunks)
  • frontend/src/modules/organization/components/details/organization-details-domains.vue (3 hunks)
  • frontend/src/modules/organization/components/details/organization-details-emails.vue (3 hunks)
  • frontend/src/modules/organization/components/details/organization-details-header.vue (2 hunks)
  • frontend/src/modules/organization/components/details/organization-details-identities.vue (3 hunks)
  • frontend/src/modules/organization/components/details/organization-details-phone-numbers.vue (3 hunks)
  • frontend/src/modules/organization/components/details/overview/community/organization-details-community-project-select.vue (3 hunks)
  • frontend/src/modules/organization/components/details/overview/organization-details-attributes.vue (2 hunks)
  • frontend/src/modules/organization/components/edit/domain/organization-domain-add.vue (5 hunks)
  • frontend/src/modules/organization/components/edit/domain/organization-domain-edit.vue (3 hunks)
  • frontend/src/modules/organization/components/edit/email/organization-email-add.vue (5 hunks)
  • frontend/src/modules/organization/components/edit/email/organization-email-edit.vue (3 hunks)
  • frontend/src/modules/organization/components/edit/identity/organization-identity-add.vue (5 hunks)
  • frontend/src/modules/organization/components/edit/identity/organization-identity-edit.vue (3 hunks)
  • frontend/src/modules/organization/components/edit/organization-add.vue (2 hunks)
  • frontend/src/modules/organization/components/edit/organization-edit-logo.vue (3 hunks)
  • frontend/src/modules/organization/components/form/organization-form-emails.vue (2 hunks)
  • frontend/src/modules/organization/components/form/organization-form-identities.vue (2 hunks)
  • frontend/src/modules/organization/components/form/organization-form-phone-number.vue (2 hunks)
  • frontend/src/modules/organization/components/lf-member/organization-lf-member-tag.vue (1 hunks)
  • frontend/src/modules/organization/components/list/organization-common-list-table.vue (4 hunks)
  • frontend/src/modules/organization/components/list/organization-list-table.vue (2 hunks)
  • frontend/src/modules/organization/components/list/organization-list-toolbar.vue (6 hunks)
  • frontend/src/modules/organization/components/organization-badge.vue (1 hunks)
  • frontend/src/modules/organization/components/organization-dropdown-content.vue (4 hunks)
  • frontend/src/modules/organization/components/organization-dropdown.vue (2 hunks)
  • frontend/src/modules/organization/components/organization-merge-suggestions-dialog.vue (2 hunks)
  • frontend/src/modules/organization/components/organization-merge-suggestions.vue (3 hunks)
  • frontend/src/modules/organization/components/organization-name.vue (2 hunks)
  • frontend/src/modules/organization/components/organization-selection-dropdown.vue (2 hunks)
  • frontend/src/modules/organization/components/organization-unmerge-dialog.vue (4 hunks)
  • frontend/src/modules/organization/components/shared/organization-dropdown.vue (2 hunks)
  • frontend/src/modules/organization/components/shared/organization-membership.vue (1 hunks)
  • frontend/src/modules/organization/components/shared/organization-select.vue (3 hunks)
  • frontend/src/modules/organization/components/shared/organization-syncing-activities.vue (2 hunks)
  • frontend/src/modules/organization/pages/organization-details.page.vue (3 hunks)
  • frontend/src/modules/organization/pages/organization-form-page.vue (2 hunks)
  • frontend/src/modules/organization/pages/organization-merge-suggestions-page.vue (6 hunks)
  • frontend/src/shared/modules/identities/components/verified-identity-badge.vue (1 hunks)
  • frontend/src/shared/modules/report-issue/component/report-data-issue-modal.vue (2 hunks)
  • frontend/src/ui-kit/timeline/Timeline.stories.ts (1 hunks)
✅ Files skipped from review due to trivial changes (43)
  • frontend/src/config/integrations/github/components/settings/github-settings-add-repository-modal.vue
  • frontend/src/modules/organization/components/form/organization-form-emails.vue
  • frontend/src/modules/contributor/components/details/contributor-details-work-history.vue
  • frontend/src/modules/contributor/components/shared/contributor-work-position.vue
  • frontend/src/modules/organization/components/details/organization-details-activities.vue
  • frontend/src/modules/organization/components/form/organization-form-phone-number.vue
  • frontend/src/modules/contributor/components/edit/affilations/contributor-affilations-edit-item.vue
  • frontend/src/modules/member/components/list/member-list-table.vue
  • frontend/src/modules/data-quality/components/organization/data-quality-organization-merge-suggestions.vue
  • frontend/src/modules/contributor/components/details/overview/contributor-details-community.vue
  • frontend/src/modules/organization/components/shared/organization-select.vue
  • frontend/src/modules/contributor/components/edit/identity/contributor-identity-edit.vue
  • frontend/src/modules/contributor/components/edit/work-history/contributor-work-history-edit.vue
  • frontend/src/modules/organization/components/organization-merge-suggestions.vue
  • frontend/src/modules/lf/layout/components/lf-menu-project-group-selection.vue
  • frontend/src/modules/organization/components/edit/domain/organization-domain-add.vue
  • frontend/src/modules/organization/components/form/organization-form-identities.vue
  • frontend/src/modules/organization/components/edit/email/organization-email-add.vue
  • frontend/src/modules/member/components/suggestions/member-merge-suggestion-dropdown.vue
  • frontend/src/modules/contributor/components/details/overview/project/contributor-details-projects-sorting.vue
  • frontend/src/shared/modules/report-issue/component/report-data-issue-modal.vue
  • frontend/src/modules/contributor/components/details/contributor-details-actions.vue
  • frontend/src/modules/contributor/components/edit/contributor-add.vue
  • frontend/src/modules/admin/modules/integration/pages/integration-status.page.vue
  • frontend/src/modules/data-quality/components/shared/data-quality-project-dropdown.vue
  • frontend/src/config/integrations/devto/components/devto-connect-drawer.vue
  • frontend/src/modules/organization/components/edit/organization-add.vue
  • frontend/src/modules/organization/components/edit/domain/organization-domain-edit.vue
  • frontend/src/modules/contributor/components/edit/affilations/contributor-affilations-edit.vue
  • frontend/src/modules/organization/components/shared/organization-syncing-activities.vue
  • frontend/src/modules/organization/components/details/organization-details-contributors.vue
  • frontend/src/modules/organization/components/details/organization-details-domains.vue
  • frontend/src/modules/organization/components/details/organization-details-phone-numbers.vue
  • frontend/src/modules/organization/components/details/organization-details-identities.vue
  • frontend/src/modules/organization/components/details/organization-details-emails.vue
  • frontend/src/modules/organization/components/details/organization-details-actions.vue
  • frontend/src/modules/organization/components/details/header/organization-details-header-logo.vue
  • frontend/src/modules/organization/components/details/overview/community/organization-details-community-project-select.vue
  • frontend/src/modules/organization/components/edit/email/organization-email-edit.vue
  • frontend/src/modules/contributor/components/details/overview/contributor-details-attributes.vue
  • frontend/src/modules/organization/components/organization-merge-suggestions-dialog.vue
  • frontend/src/modules/organization/components/list/organization-common-list-table.vue
  • frontend/src/modules/contributor/components/details/identity/contributor-details-identity-item.vue
🧰 Additional context used
🪛 GitHub Actions: Lint Frontend
frontend/src/modules/organization/components/list/organization-list-table.vue

[error] 737-737: Multiple spaces found before '/>'

frontend/src/modules/admin/modules/integration/config/status/connecting.ts

[error] 10-10: Missing space before value for key 'iconType'

frontend/src/config/integrations/discourse/components/discourse-params.vue

[error] 32-32: Unable to resolve path to module '@/ui-kit/icon/icon.vue'

frontend/src/config/integrations/devto/components/devto-params.vue

[error] 68-68: Expected 1 empty line after import statement not followed by another import

frontend/src/config/integrations/jira/components/jira-params.vue

[error] 37-37: Unable to resolve path to module '@/ui-kit/icon/icon.vue'

frontend/src/modules/contributor/components/details/header/contributor-details-header-profile-photo.vue

[error] 13-13: Multiple spaces found before ':'

frontend/src/config/integrations/confluence/components/confluence-params.vue

[error] 28-28: 'class' should be on a new line

frontend/src/modules/organization/components/organization-unmerge-dialog.vue

[error] 112-112: 'size' and 'class' attributes should be on new lines

🔇 Additional comments (89)
frontend/src/modules/organization/components/shared/organization-dropdown.vue (4)

6-6: LGTM! Icon replacement is semantically appropriate.

The new Font Awesome icon link-simple-slash appropriately represents the unmerge action.


13-13: LGTM! Icon replacement maintains semantic meaning.

The new Font Awesome icon people-group effectively represents the team organization concept.


20-20: LGTM! Icon replacement matches the danger context.

The new Font Awesome icon trash-can appropriately represents the delete action and aligns well with the danger-type dropdown item.


32-32: LGTM! Import statement correctly references the new icon component.

The import statement properly includes the new icon component from the UI kit.

frontend/src/modules/contributor/components/details/overview/contributor-details-projects.vue (3)

17-17: LGTM! Consistent tooltip icons.

The replacement of question icons with Font Awesome's circle-question maintains semantic meaning while standardizing the icon system. The implementation is consistent across both tooltips.

Also applies to: 36-36


82-82: LGTM! Clear add action icon.

The plus icon clearly communicates the add action and pairs well with the button text.


Line range hint 133-133: LGTM! Clean icon component migration.

The import changes cleanly migrate from the old icon system to Font Awesome while maintaining all functionality.

frontend/src/modules/organization/components/details/overview/organization-details-attributes.vue (2)

81-81: LGTM!

The import statement has been correctly updated to use the new icon component.


61-61: Verify the Font Awesome icon replacement.

The icon replacement from "list-view" to "rectangle-list" appears correct, but let's verify that the new icon maintains similar visual semantics for the empty state.

Run this script to check the icon name in Font Awesome's free set:

✅ Verification successful

Icon replacement is correctly implemented

The "rectangle-list" icon is a valid Font Awesome icon and is consistently used across similar components for empty state visualization. The implementation in the Icon component properly integrates with Font Awesome classes.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the icon exists in Font Awesome's free set
# and check if there are any other similar icons that might be more appropriate

rg -l "rectangle-list" frontend/src/ui-kit/icon/

Length of output: 48


Script:

#!/bin/bash
# Find the LfIcon component implementation
fd -e vue -e js -e ts "Icon.vue|icon.vue" frontend/src/ui-kit

# Search for any icon configuration or mapping files
fd "icon" frontend/src/ui-kit -t f

# Search for similar icon usages
rg -l "rectangle.*list|list.*rectangle" frontend/

Length of output: 484


Script:

#!/bin/bash
# Check the Icon component implementation
cat frontend/src/ui-kit/icon/Icon.vue

# Look for any icon name validations or mappings
rg -A 5 -B 5 "name.*prop" frontend/src/ui-kit/icon/Icon.vue

Length of output: 808

frontend/src/modules/admin/modules/projects/components/fragments/lf-project-count.vue (2)

12-12: LGTM! Clean import update.

The import statement has been correctly updated to use the new icon component from the UI kit, maintaining consistency with the project's standardization efforts.


4-4: Verify the Font Awesome icon selection.

The "layer-group" icon appears to be an appropriate replacement for the old "stack-line" icon in representing projects. However, let's verify that this icon exists in Font Awesome and maintains visual consistency with the old icon.

Run this script to check the icon's existence and any potential alternatives:

✅ Verification successful

Icon replacement is appropriate and consistent with codebase patterns

The "layer-group" icon is widely used across the codebase for project-related elements, making it a suitable replacement for the old "stack-line" icon. The usage of type="regular" is also consistent with the established pattern.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Search for usage of layer-group icon and potential alternatives
# to ensure consistency across the codebase

# Check for other usages of the layer-group icon
rg -l "layer-group" --type vue

# Check for any remaining uses of the old stack-line icon
rg -l "stack-line" --type vue

Length of output: 116


Script:

#!/bin/bash
# Find Vue files and search for icon usage patterns
fd '\.vue$' | xargs rg "layer-group" -A 1
fd '\.vue$' | xargs rg "stack-line" -A 1

# Search for both old and new icon component usage
fd '\.vue$' | xargs rg "<lf-icon-old" -A 1
fd '\.vue$' | xargs rg "<lf-icon\s+name=" -A 1

Length of output: 94356

frontend/src/modules/admin/modules/integration/config/status/done.ts (1)

9-10: LGTM! Icon update aligns with Font Awesome naming.

The change from 'checkbox-circle-fill' to 'circle-check' correctly maps to Font Awesome's icon set, and the solid style is appropriate for this status indicator.

frontend/src/modules/admin/modules/integration/config/status/error.ts (1)

9-10: LGTM! Icon update maintains visual consistency.

The change to 'circle-exclamation' maintains the circular theme established in other statuses while properly representing an error state using Font Awesome's icon set.

frontend/src/modules/admin/modules/integration/config/status/connecting.ts (1)

9-9: LGTM! Icon update preserves animation functionality.

The change to 'circle-notch' with preserved animation class properly represents the loading state using Font Awesome's icon set.

frontend/src/modules/admin/modules/integration/config/status/waiting-for-action.ts (1)

9-10: LGTM! Icon choice effectively differentiates from error state.

The change to 'triangle-exclamation' provides good visual distinction from the error state's circular icon while maintaining the warning context.

frontend/src/modules/organization/components/organization-badge.vue (1)

11-11: LGTM! Icon migration looks good.

The change from Remix icon (ri-team-line) to Font Awesome icon (people-group) is properly implemented with correct sizing and imports.

Also applies to: 19-19

frontend/src/modules/admin/modules/integration/components/integration-status.vue (1)

4-4: Verify icon configuration in integration status.

While the icon implementation looks correct, we should verify that status.status.icon and status.status.iconType are properly configured in the integration status configuration.

Also applies to: 12-12

✅ Verification successful

Icon configuration in integration status is properly implemented

All status configurations correctly define the required icon and iconType properties as specified in the IntegrationStatusConfig interface. The implementation in integration-status.vue correctly references these properties.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for integration status configuration
rg -A 10 "getIntegrationStatus" frontend/src/modules/admin/modules/integration/config/

Length of output: 1028


Script:

#!/bin/bash
# Search for IntegrationStatusConfig interface and lfIntegrationStatuses
ast-grep --pattern 'interface IntegrationStatusConfig'

# Find lfIntegrationStatuses declaration
rg -A 10 "lfIntegrationStatuses\s*=\s*" frontend/src/modules/admin/modules/integration/config/

Length of output: 153


Script:

#!/bin/bash
# Search for type definitions and status configurations in status directory
rg -t typescript "type|interface" frontend/src/modules/admin/modules/integration/config/status/

# Search for status objects with icon properties
rg -A 5 "status:\s*{" frontend/src/modules/admin/modules/integration/config/status/

Length of output: 304


Script:

#!/bin/bash
# Search for status configurations and type definitions
rg "export (const|type|interface)" frontend/src/modules/admin/modules/integration/config/status/

# Search for status objects with fixed regex
rg -A 5 '"status": {' frontend/src/modules/admin/modules/integration/config/status/

# Broader search for icon-related properties
rg "(icon|iconType)" frontend/src/modules/admin/modules/integration/config/status/

Length of output: 2016

frontend/src/shared/modules/identities/components/verified-identity-badge.vue (1)

17-21: LGTM! Icon migration looks good.

The change from verified-badge-line to badge-check is properly implemented with correct sizing and styling.

Also applies to: 26-26

frontend/src/modules/organization/components/shared/organization-membership.vue (1)

15-15: LGTM!

The import statement is correctly updated to use the new icon component.

frontend/src/modules/admin/modules/integration/config/status/index.ts (1)

14-14: LGTM!

The addition of the optional iconType property appropriately supports the migration to Font Awesome icons while maintaining backward compatibility.

frontend/src/modules/contributor/components/shared/contributor-syncing-activities.vue (1)

9-9: LGTM!

The loading icon replacement is appropriate, and the animation is preserved. The Font Awesome icon type is correctly specified.

Also applies to: 23-23

frontend/src/modules/contributor/components/shared/contributor-sentiment.vue (1)

Line range hint 4-8: LGTM! Icon replacements maintain semantic meaning.

The Font Awesome icons (face-smile, face-frown, face-meh) are appropriate replacements for the old sentiment icons, maintaining clear visual indicators of positive, negative, and neutral sentiments.

Also applies to: 17-17, 35-35, 42-42, 48-48

frontend/src/config/integrations/jira/components/jira-params.vue (1)

9-9: LGTM! Icon replacements are semantically correct.

The Font Awesome icons maintain the same visual hierarchy and meaning as the previous Remix icons.

Also applies to: 23-23

frontend/src/modules/contributor/components/details/header/contributor-details-header-profile-photo.vue (1)

13-13: LGTM! Icon replacement maintains edit functionality.

The Font Awesome sharp pen icon is an appropriate replacement for the pencil icon, maintaining clear visual indication of edit functionality.

Also applies to: 34-34

🧰 Tools
🪛 GitHub Actions: Lint Frontend

[error] 13-13: Multiple spaces found before ':'

frontend/src/modules/data-quality/components/member/data-quality-member-merge-suggestions-item.vue (1)

6-6: LGTM! Icon replacement maintains directional clarity.

The Font Awesome arrow-left icon is an appropriate replacement for the previous arrow icon, maintaining clear visual indication of the merge direction.

Also applies to: 37-37

frontend/src/modules/data-quality/components/organization/data-quality-organization-merge-suggestions-item.vue (1)

6-6: LGTM! Icon migrations look good.

The icon replacements and import statement are correctly implemented:

  • Arrow icon properly migrated to new component
  • House building icon is an appropriate choice for organization placeholder
  • Import statement correctly updated

Also applies to: 17-17, 39-39

frontend/src/modules/contributor/components/details/contributor-details-activities.vue (1)

3-3: LGTM! Icons properly migrated with animations preserved.

The icon migrations maintain functionality while improving consistency:

  • Loading spinner correctly preserves animation
  • Error icon maintains semantic meaning
  • Import statement properly updated

Also applies to: 14-14, 40-40

frontend/src/modules/admin/modules/integration/components/status/integration-platform-select.vue (1)

6-6: LGTM! Consistent icon implementation.

The icon migrations maintain consistency across the component:

  • Grid icons consistently use type="regular"
  • Icon sizes consistently set to 16px
  • Import statement properly updated

Also applies to: 13-13, 19-19, 43-43

frontend/src/config/integrations/confluence/components/confluence-params.vue (1)

10-10: LGTM! Icon replacements are consistent.

The replacement of old icons with Font Awesome icons is consistent and maintains visual hierarchy:

  • folders icon for organization count
  • folder icon for space details

Also applies to: 41-41

frontend/src/modules/organization/components/organization-name.vue (1)

15-15: LGTM! Icon replacement maintains visual consistency.

The house-building icon replacement with explicit size and text color maintains visual consistency.

frontend/src/config/integrations/devto/components/devto-params.vue (1)

10-10: LGTM! Consistent icon usage across different contexts.

The icon replacements maintain visual consistency:

  • house-building icon for organizations
  • user icon for users

Also applies to: 32-32, 52-52

frontend/src/modules/organization/components/details/organization-details-header.vue (1)

28-28: LGTM! Icon replacement maintains link visualization.

The link icon replacement with size 16 and text-gray-400 class maintains visual consistency.

frontend/src/modules/contributor/components/details/identity/contributor-details-identity-add-dropdown.vue (2)

14-20: LGTM! Icon replacement follows Font Awesome conventions.

The close icon has been properly updated to use Font Awesome's "circle-xmark" with the correct "regular" type specification.


45-45: LGTM! Email icon properly updated.

The email icon has been correctly updated to use Font Awesome's "envelope" icon with the "regular" type specification.

frontend/src/modules/contributor/components/details/header/contributor-details-header-profiles.vue (2)

20-20: LGTM! External link icons consistently updated.

The external link icons have been properly updated to use Font Awesome's "arrow-up-right-from-square" with consistent "regular" type specification across both instances.

Also applies to: 68-68


Line range hint 32-38: LGTM! Dynamic platform icon implementation.

The platform icon implementation correctly uses dynamic properties from platformData, including the new iconType property for proper Font Awesome type specification.

frontend/src/modules/organization/components/details/header/organization-details-header-profiles.vue (1)

20-20: LGTM! Consistent icon implementation with contributor profiles.

The icon replacements in this component perfectly mirror those in the contributor profiles component, maintaining consistency across the application:

  • External link icons using "arrow-up-right-from-square"
  • Dynamic platform icons with proper type specifications
  • Consistent styling and behavior

Also applies to: 32-38, 68-68

frontend/src/modules/contributor/components/edit/contributor-edit-profile-photo.vue (1)

21-24: Icon replacement looks good!

The Font Awesome circle-xmark icon is semantically equivalent to the old close-circle-line icon, maintaining the clear/remove action's visual meaning.

frontend/src/modules/data-quality/components/member/data-quality-member-issues.vue (1)

24-24: Icon replacement follows best practices!

The Font Awesome arrow-up-right-from-square icon is the standard choice for external links, making the UI more intuitive.

frontend/src/modules/data-quality/components/member/data-quality-member-merge-suggestions.vue (1)

15-15: Icon choice enhances UI clarity!

The Font Awesome eye icon paired with "View suggestion" text clearly communicates the action's purpose.

frontend/src/modules/contributor/components/details/overview/project/contributor-details-projects-affiliation.vue (1)

37-37: Consistent icon usage across organization placeholders!

The Font Awesome house-building icon is appropriately used as a placeholder for organization avatars, maintaining consistency across multiple instances.

Also applies to: 88-88

frontend/src/modules/organization/components/details/domains/organization-details-domain-item.vue (4)

8-8: LGTM! Icon replacement looks good.

The link icon is appropriately used for representing domain links, with correct size and styling.


25-25: LGTM! Verified badge icon replacement is correct.

The badge-check icon is semantically appropriate for representing verified domains.


45-45: LGTM! Action icons are consistently implemented.

The replacement icons for actions (pen, link-simple-slash, message-exclamation, trash-can) are semantically appropriate and consistently implemented.

Also applies to: 53-53, 63-63, 75-75


94-94: LGTM! Import statement is correct.

The import statement for the new icon component is properly updated.

frontend/src/modules/contributor/components/shared/contributor-dropdown.vue (3)

7-7: LGTM! Icons are correctly implemented with appropriate types.

The link-simple-slash icon and GitHub brand icon are properly implemented. The GitHub icon correctly uses type="brands" attribute.

Also applies to: 15-15


19-19: LGTM! Action icons are consistently implemented.

The replacement icons for actions (people-group, robot, trash-can) are semantically appropriate and consistently styled.

Also applies to: 23-23, 29-29


36-36: LGTM! Import statement is correct.

The import statement for the new icon component is properly updated.

frontend/src/modules/organization/components/details/identity/organization-details-identity-item.vue (3)

20-24: LGTM! Fingerprint icon is properly implemented.

The fingerprint icon replacement includes correct size and styling attributes.


53-53: LGTM! Action icons are consistently implemented.

The replacement icons for actions (ellipsis, pen, link-simple-slash, message-exclamation, trash-can) are semantically appropriate and maintain consistent styling.

Also applies to: 62-62, 70-70, 80-80, 92-92


99-99: LGTM! Import statement is correct.

The import statement for the new icon component is properly updated.

frontend/src/modules/contributor/pages/contributor-details.page.vue (3)

16-16: LGTM! Navigation icon is properly implemented.

The chevron-left icon is semantically appropriate for the back navigation button.


54-58: LGTM! Status indicator icon is properly implemented.

The circle-exclamation icon maintains the correct size and error state styling.


88-88: LGTM! Import statement is correct.

The import statement for the new icon component is properly updated.

frontend/src/modules/organization/components/edit/identity/organization-identity-add.vue (1)

8-8: LGTM! Icon replacements are consistent.

The icon replacements follow Font Awesome naming conventions and maintain visual consistency:

  • Close icon → xmark
  • Fingerprint icon → fingerprint
  • Delete icon → trash-can
  • Add icon → plus

Also applies to: 32-37, 56-56, 76-76, 103-103

frontend/src/modules/contributor/components/edit/identity/contributor-identity-add.vue (1)

8-8: LGTM! Icon replacements maintain consistency with organization component.

The icon replacements are consistent with both Font Awesome conventions and the organization-identity-add component:

  • Close icon → xmark
  • Email icon → envelope with type="regular"
  • Fingerprint icon → fingerprint
  • Delete icon → trash-can
  • Add icon → plus

Also applies to: 26-26, 33-37, 57-57, 77-77, 107-107

frontend/src/modules/organization/pages/organization-details.page.vue (1)

16-16: LGTM! Icon replacements maintain semantic meaning.

The icon replacements preserve their semantic meaning while adopting Font Awesome conventions:

  • Back navigation arrow → chevron-left
  • Warning indicator → circle-exclamation

Also applies to: 70-74, 109-109

frontend/src/modules/organization/components/list/organization-list-toolbar.vue (1)

16-16: LGTM! Icon replacements enhance action clarity.

The icon replacements in the dropdown menu and computed properties follow Font Awesome conventions while maintaining clear visual indicators:

  • Dropdown indicator → chevron-down
  • Export action → file-arrow-down
  • Merge action → shuffling
  • Team organization toggle → bookmark/bookmark-slash
  • Delete action → trash-can

Also applies to: 20-20, 41-41, 54-54, 68-68, 97-97, 128-137

frontend/src/modules/organization/components/organization-dropdown-content.vue (4)

34-34: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system.


129-129: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system.


147-148: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system while preserving the red color styling.


167-167: LGTM! Import statement added correctly.

The LfIcon component is properly imported from the ui-kit.

frontend/src/modules/organization/components/organization-unmerge-dialog.vue (2)

166-170: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system.


196-196: LGTM! Import statement added correctly.

The LfIcon component is properly imported from the ui-kit.

frontend/src/modules/organization/pages/organization-merge-suggestions-page.vue (7)

23-23: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system.


96-96: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system.


136-136: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system and correctly uses the regular type variant.


141-141: LGTM! Icon replacements look good.

The icon replacements maintain visual consistency with the new Font Awesome icon system.

Also applies to: 145-145


154-154: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system and correctly uses a larger size for the empty state illustration.


165-165: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system.


203-203: LGTM! Import statement added correctly.

The LfIcon component is properly imported from the ui-kit.

frontend/src/modules/member/components/member-dropdown-content.vue (8)

11-12: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system.


30-30: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system.


46-47: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system and correctly uses the brands type for the GitHub icon.


63-64: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system.


120-121: LGTM! Icon replacements look good.

The icon replacements maintain visual consistency with the new Font Awesome icon system.

Also applies to: 137-138


151-152: LGTM! Icon replacements look good.

The icon replacements maintain visual consistency with the new Font Awesome icon system.

Also applies to: 165-166


181-182: LGTM! Icon replacement looks good.

The icon replacement maintains visual consistency with the new Font Awesome icon system while preserving the red color styling.


203-203: LGTM! Import statement added correctly.

The LfIcon component is properly imported from the ui-kit.

frontend/src/modules/member/components/member-unmerge-dialog.vue (1)

166-170: LGTM! Consistent icon implementation.

The fingerprint icon has been consistently implemented in both dropdown menus using the new LfIcon component, maintaining visual consistency.

Also applies to: 240-244

frontend/src/modules/organization/pages/organization-form-page.vue (1)

38-38: LGTM! Appropriate icon selection.

The "arrow-turn-left" icon is semantically appropriate for the reset changes functionality.

frontend/src/modules/contributor/components/shared/contributor-engagement-level.vue (1)

5-5: LGTM! Well-implemented loading spinner.

The "circle-notch" icon with solid type is appropriately used for the loading spinner, and the animation is correctly maintained.

frontend/src/modules/organization/components/organization-dropdown.vue (1)

14-14: LGTM! Appropriate dropdown trigger icon.

The "ellipsis" icon is semantically appropriate for a dropdown menu trigger, with suitable size and type settings.

frontend/src/modules/organization/components/edit/organization-edit-logo.vue (3)

15-15: LGTM! Icon replacement looks good.

The old icon "community-line" has been appropriately replaced with the Font Awesome equivalent "house-building".


Line range hint 29-35: LGTM! Icon replacement looks good.

The old icon "close-circle-line" has been appropriately replaced with the Font Awesome equivalent "circle-xmark". The component structure and event handling are maintained.


80-80: LGTM! Import statement updated correctly.

The import statement has been updated to use the new icon component.

frontend/src/modules/organization/components/list/organization-list-table.vue (1)

834-834: LGTM! Import statement added correctly.

The import statement for the new icon component has been properly added.

frontend/src/integrations/linkedin/config.js (1)

10-11: LGTM! Verify Font Awesome icon availability.

The icon changes look good and align with Font Awesome's naming convention.

Let's verify the icon exists in Font Awesome:

✅ Verification successful

Font Awesome LinkedIn icon implementation verified ✓

The icon configuration is correct and follows the established pattern. Font Awesome is properly set up via CDN, and the LinkedIn brand icon is available in the Font Awesome library.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the Font Awesome icon is imported and used correctly

# Search for Font Awesome icon imports and usage
rg -l "linkedin.*brands" frontend/

Length of output: 36


Script:

#!/bin/bash
# Search for Font Awesome related files and configurations
echo "=== Searching for Font Awesome setup files ==="
rg -l "fontawesome|@fortawesome" frontend/

echo -e "\n=== Searching for icon type configurations ==="
rg "iconType.*['\"]brands['\"]" frontend/

echo -e "\n=== Searching for LinkedIn icon usage ==="
rg "icon.*['\"]linkedin['\"]" frontend/

Length of output: 666


Script:

#!/bin/bash
# Check Font Awesome configuration in index.html
echo "=== Checking Font Awesome setup in index.html ==="
cat frontend/index.html | grep -A 5 -B 5 "fontawesome"

Length of output: 628

frontend/src/integrations/github/config.js (1)

17-18: LGTM! Verify Font Awesome icon availability.

The icon changes look good and align with Font Awesome's naming convention.

Let's verify the icon exists in Font Awesome:

✅ Verification successful

Font Awesome icon configuration verified successfully

The icon configuration is valid and actively used across multiple components with consistent implementation.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the Font Awesome icon is imported and used correctly

# Search for Font Awesome icon imports and usage
rg -l "github.*brands" frontend/

Length of output: 177


Script:

#!/bin/bash
# Check Font Awesome setup and usage

# Search for Font Awesome package imports
echo "=== Font Awesome Package Imports ==="
rg "@fortawesome" frontend/

# Check icon usage in the found files
echo -e "\n=== Icon Usage in Components ==="
rg -A 2 -B 2 "github.*brands" frontend/

# Look for Font Awesome configuration
echo -e "\n=== Font Awesome Configuration ==="
fd -e js -e vue -e ts "font.*awesome" frontend/

Length of output: 1347


Script:

#!/bin/bash
# Check lf-icon component implementation

# Find lf-icon component
echo "=== LF Icon Component Location ==="
fd -e vue -e js -e ts "lf-icon" frontend/

# Check component content
echo -e "\n=== LF Icon Implementation ==="
rg -A 5 -B 5 "lf-icon" frontend/ --type vue --type js --type ts

Length of output: 289

@Sameh16 Sameh16 changed the base branch from main to CM-1640 January 23, 2025 11:11
@Sameh16 Sameh16 merged commit 8848046 into CM-1640 Jan 23, 2025
6 checks passed
@Sameh16 Sameh16 deleted the LFX-1640 branch January 23, 2025 11:17
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