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(@vben/common-ui): [api-select] add loading slots #5086

Closed
wants to merge 1 commit into from

Conversation

han2-n
Copy link

@han2-n han2-n commented Dec 9, 2024

Description

add loading slots

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
    • Introduced a customizable loading state in the api-select component, allowing parent components to define their own loading templates.
    • Added functionality to conditionally render content based on the loading status.

Copy link

changeset-bot bot commented Dec 9, 2024

⚠️ No Changeset found

Latest commit: 7b1921d

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 Dec 9, 2024

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.

packages/effects/common-ui/src/components/api-select/api-select.vue

Oops! Something went wrong! :(

ESLint: 9.16.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

The changes in this pull request modify the api-select.vue component to improve how loading states are managed. The direct rendering of the LoaderCircle component has been replaced with a slot-based approach, allowing parent components to define custom loading templates using the loadingSlot prop. This update enables the loading state to be passed to the slot, facilitating conditional rendering based on the loading status. The core functionality for fetching options and error handling remains unchanged.

Changes

File Path Change Summary
packages/effects/common-ui/src/components/api-select/api-select.vue Replaced direct rendering of LoaderCircle with a slot-based approach for custom loading templates. Loading state is now passed to the slot.

Possibly related PRs

  • chore: update modal.vue #4987: The changes in modal.vue enhance user experience during loading states, similar to how the api-select.vue component now allows for custom loading templates, both focusing on improving loading state handling.
  • feat: add form slot for action area #4621: While this PR introduces new slots for action areas, it shares a common theme of enhancing component flexibility through slots, akin to the slot-based loading approach in api-select.vue.

Suggested reviewers

  • vince292007
  • anncwb

🐇 In the meadow, we hop and play,
With loading states, we find our way.
A slot for loading, oh what a treat,
Custom templates make our joy complete!
So let’s celebrate this change so bright,
With flexibility, our futures are light! 🌼


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 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
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 and nitpick comments (1)
packages/effects/common-ui/src/components/api-select/api-select.vue (1)

201-203: LGTM! Consider adding accessibility attributes.

The implementation of the loading slot is well done, providing both flexibility through scoped slots and a sensible default UI. The loading state is correctly passed to the slot, allowing for custom loading indicators.

Consider adding ARIA attributes for better accessibility:

-          <LoaderCircle class="animate-spin" />
+          <LoaderCircle 
+            class="animate-spin" 
+            role="status" 
+            aria-label="Loading..."
+          />
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 018ddc7 and 7b1921d.

📒 Files selected for processing (1)
  • packages/effects/common-ui/src/components/api-select/api-select.vue (1 hunks)
🔇 Additional comments (1)
packages/effects/common-ui/src/components/api-select/api-select.vue (1)

201-203: Verify usage in parent components

The loading slot implementation looks good. To ensure proper usage, here's how parent components should implement custom loading indicators:

<api-select
  loading-slot="suffix"
  :api="fetchOptions"
>
  <template #suffix="{ loading }">
    <my-custom-spinner v-if="loading" />
  </template>
</api-select>

Let's check for existing usages to ensure compatibility:

✅ Verification successful

No breaking changes for existing ApiSelect implementations

The loading slot implementation is safe to proceed with as:

  1. No existing components are using any loading-related slots with ApiSelect
  2. The implementation provides a default loading indicator, maintaining backward compatibility
  3. The new slot is optional and won't affect current usage patterns
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for existing ApiSelect usage patterns
rg -l "ApiSelect|api-select" --type vue

# Check for any existing loading slot implementations
rg -A 3 "loading-slot" --type vue

Length of output: 131


Script:

#!/bin/bash
# Search for existing ApiSelect usage patterns without file type restriction
rg -l "ApiSelect|api-select"

# Check for any existing loading slot implementations
rg -A 3 "loading-slot"

Length of output: 546


Script:

#!/bin/bash
# Check the content of form/basic.vue files for ApiSelect usage patterns
rg -A 5 "<api-select|<ApiSelect" "playground/src/views/examples/form/basic.vue" "apps/web-naive/src/views/demos/form/basic.vue" "apps/web-ele/src/views/demos/form/basic.vue"

# Check if there are any template slots being used with ApiSelect
rg -A 5 "<template.*#.*>" "playground/src/views/examples/form/basic.vue" "apps/web-naive/src/views/demos/form/basic.vue" "apps/web-ele/src/views/demos/form/basic.vue"

Length of output: 2509

@mynetfan
Copy link
Collaborator

此PR已不适用

@mynetfan mynetfan closed this Dec 13, 2024
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.

2 participants