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

feat: integrate new component Tippy with demo #5355

Merged
merged 2 commits into from
Jan 11, 2025

Conversation

mynetfan
Copy link
Collaborator

@mynetfan mynetfan commented Jan 11, 2025

Description

添加工具提示组件 Tippy

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

    • Added Tippy.js tooltip library integration across multiple applications
    • Introduced a new Tippy demo page in the playground
    • Implemented flexible tooltip configuration options
  • Dependencies

    • Added tippy.js and vue-tippy libraries to the project
    • Integrated tooltip functionality into common UI components
  • Documentation

    • Added example page demonstrating Tippy.js usage and configuration

@mynetfan mynetfan requested review from anncwb, vince292007 and a team as code owners January 11, 2025 09:18
Copy link

changeset-bot bot commented Jan 11, 2025

⚠️ No Changeset found

Latest commit: 2978211

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

Copy link
Contributor

coderabbitai bot commented Jan 11, 2025

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

apps/web-antd/src/bootstrap.ts

Oops! Something went wrong! :(

ESLint: 9.17.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/node_modules/@vben/eslint-config/dist/index.mjs' imported from /eslint.config.mjs
at finalizeResolution (node:internal/modules/esm/resolve:257:11)
at moduleResolve (node:internal/modules/esm/resolve:914:10)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

Walkthrough

This pull request introduces Tippy.js tooltip functionality across multiple applications and the playground. The changes involve adding the initTippy function to bootstrap processes, creating a new Tippy directive and component, updating package dependencies, and adding a demo page for Tippy tooltips. The implementation provides a flexible and configurable tooltip system that can be integrated into different Vue.js applications with support for dark mode and various customization options.

Changes

File Change Summary
apps/*/src/bootstrap.ts Added initTippy(app) initialization in bootstrap process for Antd, Element, and Naive UI applications
packages/effects/common-ui/package.json Added dependencies: @vben-core/preferences, tippy.js, vue-tippy
packages/effects/common-ui/src/components/index.ts Added export for Tippy module
packages/effects/common-ui/src/components/tippy/directive.ts Created useTippyDirective for integrating Tippy.js tooltips
packages/effects/common-ui/src/components/tippy/index.ts Implemented initTippy function and Tippy component
playground/src/bootstrap.ts Added initTippy(app) initialization
playground/src/router/routes/modules/examples.ts Added new route for Tippy demo
playground/src/views/examples/tippy/index.vue Created Tippy demo component with interactive configuration
pnpm-workspace.yaml Added tippy.js and vue-tippy dependencies

Possibly related PRs

Suggested Labels

feature

Suggested Reviewers

  • vince292007

Poem

🐰 Tooltips dance with playful might,
Hopping through code, a rabbit's delight!
Tippy's magic, smooth and bright,
Enhancing UI with pure insight,
A coding bunny's joyful flight! 🎉

Finishing Touches

  • 📝 CodeRabbit is generating docstrings... (♻️ Check again to generate again)

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

@mynetfan mynetfan changed the title Feat/tippy feat: integrate new component Tippy with demo Jan 11, 2025
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: 2

🧹 Nitpick comments (5)
packages/effects/common-ui/src/components/tippy/index.ts (1)

34-39: Consider adjusting default delay values.

The current delay settings (500ms show, 200ms hide) might feel slow for power users. Consider reducing the show delay or making it configurable.

   setDefaultProps({
     allowHTML: true,
-    delay: [500, 200],
+    delay: [200, 200],
     theme: isDark.value ? '' : 'light',
     ...options,
   });
packages/effects/common-ui/src/components/tippy/directive.ts (1)

66-71: Ensure proper cleanup in unmounted hook.

The current implementation correctly destroys the tippy instance but should also remove the reference.

   unmounted(el) {
     if (el.$tippy) {
       el.$tippy.destroy();
+      delete el.$tippy;
     } else if (el._tippy) {
       el._tippy.destroy();
+      delete el._tippy;
     }
   },
playground/src/views/examples/tippy/index.vue (3)

10-33: Consider adding TypeScript types and simplifying boolean conversion.

The props and computed properties could be improved for better type safety and readability.

Consider these improvements:

-const props = reactive({
+interface TippyProps {
+  animation: string;
+  arrow: boolean;
+  content: string;
+  delay: number;
+  duration: number;
+  followCursor: string;
+  hideOnClick: string;
+  maxWidth: string;
+  placement: string;
+  theme: string;
+}
+
+const props = reactive<TippyProps>({
   animation: 'shift-away',
   arrow: true,
   content: '这是一个提示',
   // ... rest of the props
 });

 const tippyProps = computed(() => ({
   ...props,
-  followCursor: ['', 'true'].includes(props.followCursor)
-    ? !!props.followCursor
-    : props.followCursor,
-  hideOnClick: ['', 'true'].includes(props.hideOnClick)
-    ? !!props.hideOnClick
-    : props.hideOnClick,
+  followCursor: props.followCursor === '' || props.followCursor === 'true',
+  hideOnClick: props.hideOnClick === '' || props.hideOnClick === 'true',
 }));

35-159: Add form validation and consider i18n for labels.

The form configuration is comprehensive but could benefit from validation rules and internationalization.

Consider adding validation rules and extracting labels to i18n:

 const [Form] = useVbenForm({
   handleValuesChange(values) {
     Object.assign(props, { ...values });
   },
   schema: [
     {
       component: 'Select',
+      rules: [{ required: true, message: t('validation.required') }],
       componentProps: {
         class: 'w-full',
         options: [
           { label: 'shift-away', value: 'shift-away' },
           // ... options
         ],
       },
       defaultValue: props.animation,
       fieldName: 'animation',
-      label: '动画',
+      label: t('tippy.animation'),
     },
     // ... rest of the schema
   ],
 });

165-226: Enhance accessibility and extract constants.

The template could benefit from improved accessibility and constant extraction.

Consider these improvements:

+const TIPPY_DOC_URL = 'https://atomiks.github.io/tippyjs/v6/all-props/';

 function goDoc() {
-  window.open('https://atomiks.github.io/tippyjs/v6/all-props/');
+  window.open(TIPPY_DOC_URL);
 }

 <template>
   <Page title="Tippy">
     <!-- ... -->
     <Button 
+      aria-label="Open Tippy documentation"
       type="link" 
       size="small" 
       @click="goDoc"
     >
       查看文档
     </Button>
     <!-- ... -->
     <Button
+      aria-describedby="tooltip-content"
       v-tippy="'这是一个提示,使用了默认的配置'"
     >
       默认配置
     </Button>
     <!-- ... -->
   </Page>
 </template>
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4676895 and 2978211.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (11)
  • apps/web-antd/src/bootstrap.ts (2 hunks)
  • apps/web-ele/src/bootstrap.ts (2 hunks)
  • apps/web-naive/src/bootstrap.ts (2 hunks)
  • packages/effects/common-ui/package.json (2 hunks)
  • packages/effects/common-ui/src/components/index.ts (1 hunks)
  • packages/effects/common-ui/src/components/tippy/directive.ts (1 hunks)
  • packages/effects/common-ui/src/components/tippy/index.ts (1 hunks)
  • playground/src/bootstrap.ts (2 hunks)
  • playground/src/router/routes/modules/examples.ts (1 hunks)
  • playground/src/views/examples/tippy/index.vue (1 hunks)
  • pnpm-workspace.yaml (2 hunks)
🧰 Additional context used
🪛 Biome (1.9.4)
packages/effects/common-ui/src/components/tippy/directive.ts

[error] 25-25: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)


[error] 31-31: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)


[error] 37-37: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)


[error] 43-43: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)


[error] 49-49: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)

⏰ Context from checks skipped due to timeout of 90000ms (9)
  • GitHub Check: Check (windows-latest)
  • GitHub Check: Check (ubuntu-latest)
  • GitHub Check: Test (windows-latest)
  • GitHub Check: Test (ubuntu-latest)
  • GitHub Check: Lint (windows-latest)
  • GitHub Check: post-update (windows-latest)
  • GitHub Check: Lint (ubuntu-latest)
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: post-update (ubuntu-latest)
🔇 Additional comments (11)
packages/effects/common-ui/src/components/index.ts (1)

8-8: LGTM! Export follows the established pattern.

The new Tippy export follows the consistent barrel file pattern used for other component exports.

apps/web-naive/src/bootstrap.ts (2)

4-4: LGTM! Import follows the established pattern.

The import is correctly placed with other @VBen imports.


32-34: Verify consistent Tippy initialization across apps.

The initialization timing looks correct, placed after access directive registration. However, let's verify the consistency across all apps.

✅ Verification successful

Tippy initialization is consistent across all apps

All apps (web-antd, web-ele, web-naive, and playground) initialize Tippy in the same way:

  • Imported from @vben/common-ui
  • Initialized after access directive registration
  • Initialized before router configuration
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify consistent Tippy initialization across all apps
# Expected: All apps should initialize Tippy in the same order

# Check initialization order in all bootstrap files
echo "Checking bootstrap files for Tippy initialization:"
rg -B 2 -A 2 "initTippy\(app\)" "apps/*/src/bootstrap.ts" "playground/src/bootstrap.ts"

Length of output: 452


Script:

#!/bin/bash
# Find all bootstrap.ts files and check Tippy initialization
echo "Locating bootstrap.ts files:"
fd bootstrap.ts

echo -e "\nChecking Tippy initialization in these files:"
fd bootstrap.ts --exec rg -B 5 -A 5 "initTippy"

Length of output: 2063

apps/web-antd/src/bootstrap.ts (1)

4-4: LGTM! Changes maintain consistency with other apps.

The import and initialization of Tippy follow the same pattern as in other apps, maintaining consistency across the codebase.

Also applies to: 33-35

playground/src/bootstrap.ts (1)

4-4: LGTM! Consistent implementation across all apps confirmed.

The import and initialization of Tippy maintain consistency with other apps, completing a uniform implementation across the codebase.

Also applies to: 34-36

apps/web-ele/src/bootstrap.ts (1)

4-4: LGTM! Proper initialization of Tippy.

The initialization is correctly placed after core functionality setup and before mounting the app.

Also applies to: 36-37

packages/effects/common-ui/src/components/tippy/index.ts (1)

40-44: Potential reactivity issue with theme handling.

The theme watchEffect is only set up if theme is not provided in options. This might cause issues if options.theme is initially set but later changes to 'auto'.

Consider moving the watchEffect outside the condition:

-  if (!options || !Reflect.has(options, 'theme') || options.theme === 'auto') {
     watchEffect(() => {
-      setDefaultProps({ theme: isDark.value ? '' : 'light' });
+      if (!options?.theme || options.theme === 'auto') {
+        setDefaultProps({ theme: isDark.value ? '' : 'light' });
+      }
     });
-  }
playground/src/router/routes/modules/examples.ts (1)

251-259: LGTM! Route configuration follows existing patterns.

The Tippy demo route is properly configured with appropriate icon and title.

packages/effects/common-ui/package.json (1)

25-25: LGTM! Dependencies added for Tippy integration.

The new dependencies are correctly added and align with the PR objectives for implementing tooltip functionality.

Also applies to: 36-36, 39-39

pnpm-workspace.yaml (1)

159-159: Verify Tippy.js dependency versions for security and compatibility.

Let's verify that the specified versions are up-to-date and secure:

Also applies to: 179-179

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

1-9: LGTM! Well-structured imports and setup.

The component setup and imports are well-organized and follow Vue 3 best practices.

Copy link
Contributor

coderabbitai bot commented Jan 11, 2025

Caution

An unexpected error occurred while opening a pull request: Not Found - https://docs.github.com/rest/git/refs#get-a-reference

@mynetfan mynetfan merged commit a263731 into vbenjs:main Jan 11, 2025
13 of 15 checks passed
@mynetfan mynetfan deleted the feat/tippy branch January 11, 2025 09:36
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