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

fix(vue-directive): unify the functions in vue-hooks into double-layer functions and optimize the infinite-scroll function #2864

Merged
merged 1 commit into from
Feb 7, 2025

Conversation

shenjunjian
Copy link
Collaborator

@shenjunjian shenjunjian commented Feb 7, 2025

PR

统一vue-hooks为双层函数
优化无限滚动指令,内部的函数getScrollContainer使用utils函数代替

PR Checklist

Please check if your PR fulfills the following requirements:

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

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • New Features
    • Consolidated infinite scrolling is now available with an improved default integration for smoother list navigation.

  • Refactor
    • Enhanced handling of scrollable containers along with updates to floating element and lazy-loading behaviors using modern reactive patterns for a more consistent and flexible user experience.

…r functions and optimize the infinite-scroll function
Copy link

coderabbitai bot commented Feb 7, 2025

Walkthrough

This pull request refactors several packages by removing the dependency on @opentiny/vue-directive and updating related imports. In the renderless package, the getScrollContainer function is now imported from @opentiny/utils. The vue-directive package has its exports adjusted to remove getScrollContainer and include InfiniteScroll as the default export, along with the removal of redundant utility functions. In vue-hooks, the dependency on @opentiny/vue-common is removed and the useFloating and useLazyShow functions are updated to accept destructured parameters.

Changes

File(s) Change Summary
packages/renderless/package.json
packages/renderless/src/recycle-scroller/index.ts
Removed dependency on @opentiny/vue-directive and updated the import for getScrollContainer to use @opentiny/utils.
packages/vue-directive/index.ts
packages/vue-directive/src/infinite-scroll.ts
Removed export of getScrollContainer and added InfiniteScroll to exports; eliminated redundant utility functions; changed export of InfiniteScroll to default.
packages/vue-hooks/package.json
packages/vue-hooks/src/use-floating.ts
packages/vue-hooks/src/use-lazy-show.ts
Removed dependency on @opentiny/vue-common; refactored useFloating and useLazyShow to accept destructured parameters and updated their function signatures.

Possibly related PRs

Suggested labels

enhancement, refactoring

Suggested reviewers

  • zzcr

Poem

I’m a rabbit with a code-hop beat,
Trimming dependencies both sleek and neat,
With hooks and exports now set just right,
My ASCII ears perk in digital light 🐇,
Hopping through refactors in the moonlit night.
Cheers to cleaner code in every byte!

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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.

@github-actions github-actions bot added the bug Something isn't working label Feb 7, 2025
Copy link

Walkthrough

This PR refactors the vue-hooks to use double-layer functions and optimizes the infinite-scroll directive by replacing the internal getScrollContainer function with a utility function. It aims to enhance the modularity and efficiency of the code.

Changes

File Summary
packages/renderless/package.json Updated package dependencies.
packages/renderless/src/recycle-scroller/index.ts Replaced getScrollContainer import from @opentiny/vue-directive to @opentiny/utils.
packages/vue-directive/index.ts Adjusted exports to include InfiniteScroll from a different path.
packages/vue-directive/src/infinite-scroll.ts Removed duplicate functions and refactored InfiniteScroll to use default export.
packages/vue-hooks/package.json Updated package dependencies.
packages/vue-hooks/src/use-floating.ts Refactored to use double-layer functions for better modularity.
packages/vue-hooks/src/use-lazy-show.ts Refactored to use double-layer functions for better modularity.

@@ -1,4 +1,5 @@
import { throttle } from '@opentiny/utils'
import { getScrollContainer } from '@opentiny/utils'

Choose a reason for hiding this comment

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

Ensure that the getScrollContainer function from @opentiny/utils provides the same functionality as the previous implementation to avoid any potential issues.

Copy link

github-actions bot commented Feb 7, 2025

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide

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: 0

🧹 Nitpick comments (4)
packages/vue-hooks/src/use-lazy-show.ts (1)

14-18: Consider adding type annotations for better maintainability.

While the code functions correctly, adding TypeScript type annotations for the destructured parameters would improve code maintainability and IDE support.

-  ({ ref, watch, isRef }) =>
+  ({ ref, watch, isRef }: { ref: Function; watch: Function; isRef: Function }) =>
packages/vue-directive/src/infinite-scroll.ts (1)

165-172: Consider adding JSDoc for the exported directive.

Adding JSDoc documentation for the exported directive would improve code documentation and maintainability.

+/**
+ * Infinite scroll directive
+ * @example
+ * <div v-infinite-scroll="loadMore">...</div>
+ */
 export default {
   bind,
   update,
packages/vue-hooks/src/use-floating.ts (2)

329-342: Consider adding return type annotation for virtualEl function.

Adding a return type annotation would improve type safety and documentation.

-const virtualEl = (x: number, y: number, w = 0, h = 0) => ({
+const virtualEl = (x: number, y: number, w = 0, h = 0): ReferenceElement => ({

348-360: Consider extracting state initialization into a separate function.

The state initialization logic could be extracted into a separate function for better readability and maintainability.

+const initializeState = (state: IFloatOption, markRaw: Function) => {
+  Object.keys(defaultOption).forEach((key) => {
+    if (!Object.prototype.hasOwnProperty.call(state, key)) {
+      state[key] = defaultOption[key]
+    }
+  })
+  state._last = markRaw({}) as any
+  state._events = markRaw({ show: [], hide: [], update: [] })
+}
+
 const state = reactive(option) as IFloatOption
-Object.keys(defaultOption).forEach((key) => {
-  if (!Object.prototype.hasOwnProperty.call(state, key)) {
-    state[key] = defaultOption[key]
-  }
-})
-state._last = markRaw({}) as any
-state._events = markRaw({ show: [], hide: [], update: [] })
+initializeState(state, markRaw)
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2581baa and 951a52b.

📒 Files selected for processing (7)
  • packages/renderless/package.json (0 hunks)
  • packages/renderless/src/recycle-scroller/index.ts (1 hunks)
  • packages/vue-directive/index.ts (1 hunks)
  • packages/vue-directive/src/infinite-scroll.ts (2 hunks)
  • packages/vue-hooks/package.json (1 hunks)
  • packages/vue-hooks/src/use-floating.ts (2 hunks)
  • packages/vue-hooks/src/use-lazy-show.ts (1 hunks)
💤 Files with no reviewable changes (1)
  • packages/renderless/package.json
✅ Files skipped from review due to trivial changes (1)
  • packages/renderless/src/recycle-scroller/index.ts
🔇 Additional comments (5)
packages/vue-hooks/src/use-lazy-show.ts (1)

11-13: LGTM! Clean dependency injection pattern.

The refactoring to accept hooks as parameters improves testability and modularity by removing direct dependencies.

packages/vue-directive/index.ts (1)

16-20: LGTM! Clean export organization.

The exports are now properly organized and the utility function has been moved to a more appropriate location.

packages/vue-directive/src/infinite-scroll.ts (1)

1-2: LGTM! Good use of shared utilities.

Importing getScrollContainer from @opentiny/utils reduces code duplication and improves maintainability.

packages/vue-hooks/src/use-floating.ts (1)

345-347: LGTM! Clean dependency injection pattern.

The refactoring to accept hooks as parameters improves testability and modularity by removing direct dependencies.

packages/vue-hooks/package.json (1)

16-19: Dependency Change: Verification of Updated Dependencies

The removal of "@opentiny/vue-common" and the inclusion of "@opentiny/utils" with workspace versioning are in line with the PR objectives. Please confirm that all modules previously relying on "@opentiny/vue-common" have been appropriately refactored to use the updated utility functions. It would also be beneficial to document this breaking dependency change in the release notes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants