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

perf: all icons used in the core are offline #4173

Merged
merged 3 commits into from
Aug 17, 2024
Merged

perf: all icons used in the core are offline #4173

merged 3 commits into from
Aug 17, 2024

Conversation

anncwb
Copy link
Collaborator

@anncwb anncwb commented Aug 17, 2024

Description

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
  • Run the tests with pnpm test.
  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

  • New Features

    • Updated routing paths for the 'VbenAbout' component across multiple modules, simplifying access.
    • Introduced new icons to the application, enhancing the visual representation of various features.
    • Added new props to the VbenScrollbar component for improved customization.
  • Bug Fixes

    • Resolved potential visual confusion during tab drag operations by adjusting class handling.
  • Documentation

    • Updated dependency versions in relevant package files, ensuring the use of the latest features and improvements.

@anncwb anncwb requested review from vince292007 and a team as code owners August 17, 2024 12:58
Copy link

changeset-bot bot commented Aug 17, 2024

⚠️ No Changeset found

Latest commit: a7bd65a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@anncwb anncwb added the perf label Aug 17, 2024
Copy link
Contributor

coderabbitai bot commented Aug 17, 2024

Warning

Rate limit exceeded

@anncwb has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 5 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 09c51bc and a7bd65a.

Walkthrough

The recent changes in the application involve updates to routing configurations, specifically the VbenAbout component path across multiple files, indicating a restructuring for clarity. Additional updates include minor dependency version upgrades and the enhancement of various Vue components, particularly in icon usage and styling. These adjustments aim to improve code organization, readability, and the user interface without altering core functionalities.

Changes

Files Change Summary
apps/web-antd/src/router/routes/modules/vben.ts, Updated the component path for VbenAbout from #/views/_core/vben/about/index.vue to #/views/_core/about/index.vue.
apps/web-ele/src/router/routes/modules/vben.ts, Same as above for the VbenAbout route component path.
apps/web-naive/src/router/routes/modules/vben.ts, Same as above for the VbenAbout route component path.
playground/src/router/routes/modules/vben.ts Same as above for the VbenAbout route component path.
docs/src/guide/essentials/route.md Updated VbenAbout route component import path from #/views/_core/vben/about/index.vue to #/views/_core/about/index.vue.
docs/package.json Upgraded vitepress package from ^1.3.2 to ^1.3.3.
internal/tailwind-config/package.json Updated @iconify/json version from ^2.2.237 to ^2.2.238.
package.json Updated @types/node to ^22.4.0 and cspell to ^8.14.1.
packages/@core/base/icons/src/create-icon.ts Changed the name property format from SvgIcon-${icon} to Icon-${icon}.
packages/@core/base/icons/src/index.ts Removed export statement for Material Design Icons.
packages/@core/base/icons/src/lucide.ts Added new icon exports and renamed existing ones for clarity.
packages/@core/ui-kit/layout-ui/src/components/layout-content.vue Removed a commented-out line for a <BlurShadow> component.
packages/@core/ui-kit/layout-ui/src/components/widgets/sidebar-collapse-button.vue Updated icons for sidebar collapse button. Removed transition classes affecting animation behavior.
packages/@core/ui-kit/layout-ui/src/components/widgets/sidebar-fixed-button.vue Replaced icons and adjusted padding class for clarity.
packages/@core/ui-kit/shadcn-ui/src/components/scrollbar/scrollbar.vue Renamed computed properties for scrollbar shadow classes.
packages/@core/ui-kit/tabs-ui/src/components/tabs-chrome/tabs.vue Updated icon imports and adjusted transition names for better user experience.
packages/@core/ui-kit/tabs-ui/src/components/tabs/tabs.vue Replaced icon imports and modified transition effects for tabs.
packages/@core/ui-kit/tabs-ui/src/tabs-view.vue Added new props for scrollbar shadow control.
packages/effects/layouts/src/basic/tabbar/use-tabbar.ts Updated pinned tab icons while maintaining existing functionality.
packages/icons/src/iconify/index.ts Uncommented and added new icon exports to expand the available icon library.
packages/locales/package.json Incremented versions of @intlify/core-base and vue-i18n.

Poem

🐇 In the code where rabbits roam,
Changes made to call it home.
Paths restructured, icons bright,
Bringing joy and pure delight.
With each update, we hop and cheer,
A cleaner codebase, oh so dear! 🌟


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 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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

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

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (4)
packages/icons/src/iconify/index.ts (1)

9-9: MdiGithub Icon Usage Not Found

The MdiGithub icon is defined but not used anywhere in the codebase. Ensure that this export is utilized where necessary or intended. If it is meant for future use, consider documenting this for clarity.

  • Location: packages/icons/src/iconify/index.ts
Analysis chain

LGTM! Verify usage of MdiGithub.

The MdiGithub icon is a new addition to the icon library.

Ensure that it is utilized correctly in the application.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of `MdiGithub` in the codebase.

# Test: Search for occurrences of `MdiGithub`. Expect: Intentional usage.
rg --type ts -A 3 $'MdiGithub'

Length of output: 291

packages/@core/base/icons/src/lucide.ts (2)

6-6: Unused Alias Detected: MdiMenuClose

The alias MdiMenuClose for ArrowRightFromLine is defined but not used anywhere else in the codebase. Consider removing it if it's not intended for future use.

  • File: packages/@core/base/icons/src/lucide.ts
Analysis chain

LGTM! Verify usage of MdiMenuClose.

Aliasing ArrowRightFromLine as MdiMenuClose provides clarity in usage.

Ensure that the alias is utilized correctly in the application.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of `MdiMenuClose` alias in the codebase.

# Test: Search for occurrences of `MdiMenuClose`. Expect: Intentional usage.
rg --type ts -A 3 $'MdiMenuClose'

Length of output: 279


Script:

#!/bin/bash
# Description: Verify the usage of `MdiMenuClose` alias in the entire codebase across all file types.

# Test: Search for occurrences of `MdiMenuClose` in all file types. Expect: Intentional usage.
rg -A 3 $'MdiMenuClose'

Length of output: 269


4-4: Unused Alias: MdiMenuOpen

The alias MdiMenuOpen for ArrowLeftFromLine is defined but not used elsewhere in the codebase. Consider removing the alias if it is not intended for immediate use or documentation purposes.

  • Location: packages/@core/base/icons/src/lucide.ts
Analysis chain

LGTM! Verify usage of MdiMenuOpen.

Aliasing ArrowLeftFromLine as MdiMenuOpen provides clarity in usage.

Ensure that the alias is utilized correctly in the application.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of `MdiMenuOpen` alias in the codebase.

# Test: Search for occurrences of `MdiMenuOpen`. Expect: Intentional usage.
rg --type ts -A 3 $'MdiMenuOpen'

Length of output: 302


Script:

#!/bin/bash
# Description: Search for imports or usages of `MdiMenuOpen` across the codebase.

# Test: Find any import or usage of `MdiMenuOpen`. Expect: Confirm usage or lack thereof.
rg --type ts --type tsx -A 3 'import.*MdiMenuOpen|MdiMenuOpen'

Length of output: 92


Script:

#!/bin/bash
# Description: Search for imports or usages of `MdiMenuOpen` across the codebase.

# Test: Find any import or usage of `MdiMenuOpen`. Expect: Confirm usage or lack thereof.
rg --type-add 'tsx:*.{ts,tsx}' --type tsx -A 3 'import.*MdiMenuOpen|MdiMenuOpen'

Length of output: 353

packages/@core/ui-kit/tabs-ui/src/tabs-view.vue (1)

67-67: Remove the extra space in scroll-bar-class.

The extra space at the end of the scroll-bar-class string may affect CSS styling or class application. Consider removing it for consistency.

- scroll-bar-class="z-10 hidden "
+ scroll-bar-class="z-10 hidden"
Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6680858 and 09c51bc.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (23)
  • apps/web-antd/src/router/routes/modules/vben.ts (1 hunks)
  • apps/web-ele/src/router/routes/modules/vben.ts (1 hunks)
  • apps/web-naive/src/router/routes/modules/vben.ts (1 hunks)
  • docs/package.json (1 hunks)
  • docs/src/guide/essentials/route.md (1 hunks)
  • internal/tailwind-config/package.json (1 hunks)
  • package.json (2 hunks)
  • packages/@core/base/icons/src/create-icon.ts (1 hunks)
  • packages/@core/base/icons/src/index.ts (1 hunks)
  • packages/@core/base/icons/src/lucide.ts (3 hunks)
  • packages/@core/ui-kit/layout-ui/src/components/layout-content.vue (1 hunks)
  • packages/@core/ui-kit/layout-ui/src/components/widgets/sidebar-collapse-button.vue (2 hunks)
  • packages/@core/ui-kit/layout-ui/src/components/widgets/sidebar-fixed-button.vue (2 hunks)
  • packages/@core/ui-kit/shadcn-ui/src/components/scrollbar/scrollbar.vue (3 hunks)
  • packages/@core/ui-kit/tabs-ui/src/components/tabs-chrome/tabs.vue (3 hunks)
  • packages/@core/ui-kit/tabs-ui/src/components/tabs/tabs.vue (4 hunks)
  • packages/@core/ui-kit/tabs-ui/src/tabs-view.vue (1 hunks)
  • packages/@core/ui-kit/tabs-ui/src/use-tabs-drag.ts (1 hunks)
  • packages/effects/layouts/src/basic/tabbar/use-tabbar.ts (2 hunks)
  • packages/icons/src/iconify/index.ts (1 hunks)
  • packages/locales/package.json (1 hunks)
  • playground/src/router/routes/modules/vben.ts (1 hunks)
  • playground/src/views/examples/ellipsis/index.vue (1 hunks)
Files skipped from review due to trivial changes (12)
  • apps/web-naive/src/router/routes/modules/vben.ts
  • docs/package.json
  • docs/src/guide/essentials/route.md
  • internal/tailwind-config/package.json
  • package.json
  • packages/@core/base/icons/src/create-icon.ts
  • packages/@core/base/icons/src/index.ts
  • packages/@core/ui-kit/layout-ui/src/components/layout-content.vue
  • packages/@core/ui-kit/layout-ui/src/components/widgets/sidebar-fixed-button.vue
  • packages/@core/ui-kit/shadcn-ui/src/components/scrollbar/scrollbar.vue
  • packages/effects/layouts/src/basic/tabbar/use-tabbar.ts
  • packages/locales/package.json
Additional comments not posted (23)
packages/icons/src/iconify/index.ts (4)

11-11: LGTM! Verify usage of MdiGoogle.

The MdiGoogle icon is a new addition to the icon library.

Ensure that it is utilized correctly in the application.


7-7: LGTM! Verify usage of MdiWechat.

The MdiWechat icon is a new addition to the icon library.

Ensure that it is utilized correctly in the application.


5-5: LGTM! Verify usage of MdiKeyboardEsc.

Uncommenting the export makes the MdiKeyboardEsc icon available for use.

Ensure that this change aligns with the project's requirements and verify its usage in the codebase.


13-13: LGTM! Verify usage of MdiQqchat.

The MdiQqchat icon is a new addition to the icon library.

Ensure that it is utilized correctly in the application.

packages/@core/ui-kit/layout-ui/src/components/widgets/sidebar-collapse-button.vue (2)

2-2: LGTM! Verify availability of ChevronsLeft and ChevronsRight.

The import statement includes new icons for the sidebar collapse button.

Ensure that these icons are available in the icon library.

Verification successful

Icons ChevronsLeft and ChevronsRight are available. The icons are correctly exported from the lucide.ts file, confirming their availability for use in the project.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the availability of `ChevronsLeft` and `ChevronsRight` in the icon library.

# Test: Search for the export of `ChevronsLeft` and `ChevronsRight`. Expect: Icons are exported correctly.
rg --type ts -A 3 $'ChevronsLeft|ChevronsRight'

Length of output: 321


13-17: LGTM! Verify impact of removed transition classes.

The template uses new icons and removes transition classes.

Ensure that the removal of transition-all duration-300 does not negatively impact the UI/UX.

packages/@core/base/icons/src/lucide.ts (5)

17-17: LGTM! Verify usage of ChevronsRight.

The ChevronsRight icon is a new addition to the icon library.

Ensure that it is utilized correctly in the application.


21-21: LGTM! Verify usage of IconDefault.

Renaming Disc3 to Disc and aliasing as IconDefault may simplify usage.

Ensure that the alias is utilized correctly in the application.


16-16: LGTM! Verify usage of ChevronsLeft.

The ChevronsLeft icon is a new addition to the icon library.

Ensure that it is utilized correctly in the application.


43-43: LGTM! Verify usage of Pin.

The Pin icon is a new addition to the icon library.

Ensure that it is utilized correctly in the application.

Verification successful

Verification complete: Pin icon usage is appropriate.

The Pin icon is used in a UI component for toggling pin states, which is a suitable application of this icon.

  • File: packages/effects/layouts/src/basic/tabbar/use-tabbar.ts
  • Context: Used to toggle tab pinning with conditional logic.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of `Pin` in the codebase.

# Test: Search for occurrences of `Pin`. Expect: Intentional usage.
rg --type ts -A 3 $'Pin'

Length of output: 6833


44-44: LGTM! Verify usage of PinOff.

The PinOff icon is a new addition to the icon library.

Ensure that it is utilized correctly in the application.

Verification successful

Usage of PinOff is verified and appropriate.

The PinOff icon is used in the use-tabbar.ts file to conditionally represent a toggle state for pinning or unpinning, indicating intentional and correct usage.

  • File: packages/effects/layouts/src/basic/tabbar/use-tabbar.ts
  • Usage Context: Conditional assignment to an icon property.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of `PinOff` in the codebase.

# Test: Search for occurrences of `PinOff`. Expect: Intentional usage.
rg --type ts -A 3 $'PinOff'

Length of output: 871

apps/web-ele/src/router/routes/modules/vben.ts (1)

29-29: Verify the existence of the component at the new path.

The path for the VbenAbout component has been updated. Ensure that the component exists at #/views/_core/about/index.vue.

Verification successful

Component Exists at the New Path

The index.vue file for the VbenAbout component exists at the specified path apps/web-ele/src/views/_core/about/index.vue. This confirms that the component is correctly located at the updated path.

  • Verified path: apps/web-ele/src/views/_core/about/index.vue
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the component at the new path.

# Test: Check if the file exists at the new path. Expect: File should exist.
fd 'index.vue' --exec rg --files-with-matches '#/views/_core/about/index.vue'

Length of output: 77


Script:

#!/bin/bash
# Description: Verify the existence of the component at the new path using a direct approach.

# Test: Check if the file exists at the specified path.
fd 'index.vue' | grep '/views/_core/about/index.vue'

Length of output: 231

apps/web-antd/src/router/routes/modules/vben.ts (1)

29-29: Verify the existence of the component at the new path.

The path for the VbenAbout component has been updated. Ensure that the component exists at #/views/_core/about/index.vue.

playground/src/views/examples/ellipsis/index.vue (1)

19-19: Increase in max-width improves readability.

The change to max-width from 240 to 500 allows more text to be visible before truncation, enhancing readability.

playground/src/router/routes/modules/vben.ts (1)

30-30: Verify the new component path.

Ensure that the new path #/views/_core/about/index.vue is correct and that the VbenAbout component is accessible at this location. This change may affect how the application resolves and loads the component.

Verification successful

Component path verified successfully.

The index.vue file exists at the specified path playground/src/views/_core/about/index.vue, confirming that the component is accessible and the import path in the routing configuration is correct.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the `index.vue` file at the new path.

# Test: Check if the file exists at the specified path.
fd 'index.vue' | grep 'views/_core/about/index.vue'

Length of output: 230

packages/@core/ui-kit/tabs-ui/src/tabs-view.vue (1)

63-64: Props added to VbenScrollbar.

The :shadow-bottom and :shadow-top props are set to false, which will alter the visual presentation of the scrollbar by removing shadows. Ensure this aligns with the desired UI design.

packages/@core/ui-kit/tabs-ui/src/use-tabs-drag.ts (1)

34-34: Clarify the change in resetElState.

The line removing the 'dragging' class from el is commented out. This may cause the parent element to retain the 'dragging' class, potentially leading to confusion. Confirm if this behavior is intentional and aligns with the desired drag-and-drop functionality.

packages/@core/ui-kit/tabs-ui/src/components/tabs/tabs.vue (3)

68-68: Transition direction change approved.

The transition effect changed from slide-left to slide-right, which alters the animation direction. Ensure this aligns with the intended UI/UX design.

Consider verifying with the design team to confirm this change meets design expectations.


80-80: Class attribute change approved.

The addition of translate-all likely enhances hover effects and visual transitions. Ensure this change maintains visual consistency across different browsers and devices.

Consider testing the component across various environments to confirm consistent behavior.


8-8: Import change approved.

The import of MdiPin has been replaced with Pin, aligning with the PR objective to ensure offline icons.

Verify that Pin is correctly used throughout the component.

Verification successful

Pin icon usage verified.

The Pin icon is used correctly throughout the component as expected.

  • Instances of <Pin were found in the .vue files.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of the `Pin` icon in the codebase.

# Test: Search for the usage of `Pin`. Expect: Correct usage in relevant components.
rg --type vue -A 5 $'<Pin'

Length of output: 55


Script:

#!/bin/bash
# Find all .vue files and search for the usage of <Pin within them
fd --extension vue --exec rg '<Pin' {}

Length of output: 369

packages/@core/ui-kit/tabs-ui/src/components/tabs-chrome/tabs.vue (3)

65-65: Transition direction change approved.

The transition effect changed from slide-left to slide-right, which alters the animation direction. Ensure this aligns with the intended UI/UX design.

Consider verifying with the design team to confirm this change meets design expectations.


73-73: Class attribute change approved.

The addition of translate-all likely enhances hover effects and visual transitions. Ensure this change maintains visual consistency across different browsers and devices.

Consider testing the component across various environments to confirm consistent behavior.


8-8: Import change approved.

The import of MdiPin has been replaced with Pin, aligning with the PR objective to ensure offline icons.

Verify that Pin is correctly used throughout the component.

Verification successful

Usage of Pin Icon Verified

The Pin component is correctly used in the tabs.vue and tabs-chrome/tabs.vue components. The usage aligns with the intended functionality, ensuring that the icon is displayed conditionally based on the component's logic.

  • File: packages/@core/ui-kit/tabs-ui/src/components/tabs/tabs.vue
  • File: packages/@core/ui-kit/tabs-ui/src/components/tabs-chrome/tabs.vue

The import and usage of the Pin icon are consistent and correct across the relevant components.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of the `Pin` icon in the codebase.

# Test: Search for the usage of `Pin`. Expect: Correct usage in relevant components.
rg --type vue -A 5 $'<Pin'

Length of output: 55


Script:

#!/bin/bash
# Description: Verify the usage of the `Pin` icon in the codebase.

# Test: Search for the usage of `Pin`. Expect: Correct usage in relevant components.
rg -A 5 '<Pin'

Length of output: 5672

@anncwb anncwb merged commit 3c17f4e into main Aug 17, 2024
15 checks passed
@anncwb anncwb deleted the perf/icons branch August 17, 2024 13:11
@github-actions github-actions bot locked and limited conversation to collaborators Sep 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant