Skip to content

perf: improve modal and drawer component documentation and fix known problems - #4264

Merged
anncwb merged 2 commits into
mainfrom
feature/popup-doc
Aug 28, 2024
Merged

perf: improve modal and drawer component documentation and fix known problems#4264
anncwb merged 2 commits into
mainfrom
feature/popup-doc

Conversation

@anncwb

@anncwb anncwb commented Aug 28, 2024

Copy link
Copy Markdown
Collaborator

…problems

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

    • Introduced a labeling system for pull requests to enhance organization and visibility.
    • Added a new job for deploying documentation in the CI workflow.
    • Implemented a new component for accessing documentation directly from the UI.
    • Added support for a dynamic drawer and modal interface with enhanced functionality.
  • Improvements

    • Updated documentation to clarify usage and enhance user experience.
    • Enhanced the modal and drawer components with dynamic data handling capabilities.
    • Improved loading state management in modal and drawer components for better user engagement.
  • Bug Fixes

    • Removed unused code and comments to streamline functionality and improve performance.

@anncwb
anncwb requested review from a team and vince292007 as code owners August 28, 2024 14:09
@changeset-bot

changeset-bot Bot commented Aug 28, 2024

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 6b96a5c

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 documentation Improvements or additions to documentation enhancement New feature or request labels Aug 28, 2024
@github-actions github-actions Bot added feature and removed enhancement New feature or request labels Aug 28, 2024
@coderabbitai

coderabbitai Bot commented Aug 28, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The changes involve the introduction of a new GitHub Actions labeling system, modifications to existing workflows, and enhancements to documentation components. New Vue components for dynamic drawers and modals were added, while existing ones were refined for improved functionality. Additionally, updates to the project's documentation provide clearer usage instructions and enhance accessibility for users.

Changes

File(s) Change Summary
.github/labeler.yml, .github/release-drafter.yml, .github/workflows/deploy.yml, .github/workflows/labeler.yml New workflows and labeling configurations introduced, including updates to existing label categories.
docs/.vitepress/config/zh.mts, docs/src/components/common-ui/vben-drawer.md, docs/src/components/common-ui/vben-modal.md Documentation updates for sidebar items and component explanations, enhancing clarity and usability.
docs/src/demos/vben-drawer/*.vue, docs/src/demos/vben-modal/*.vue, playground/src/views/examples/*.vue New demo components added for drawers and modals, with updates to existing ones for dynamic functionality and improved user interactions.
packages/@core/ui-kit/popup-ui/src/modal/*.ts, packages/@core/ui-kit/popup-ui/src/modal/modal.vue Modifications to modal logic, including header display options and loading state management, streamlining functionality.
packages/stores/src/modules/tabbar.ts, packages/utils/src/helpers/generate-routes-backend.ts Minor comment and documentation updates for clarity, with no functional changes.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Drawer
    participant Modal
    participant Documentation

    User->>Drawer: Open drawer
    Drawer->>User: Show content
    User->>Drawer: Update content
    Drawer->>User: Refresh display

    User->>Modal: Open modal
    Modal->>User: Show data
    User->>Modal: Confirm actions
    Modal->>User: Process confirmation
Loading

🐰 Hopping through the code, oh what a delight,
New workflows and features make everything bright!
With drawers and modals that dance and sway,
Documentation clearer, guiding the way.
Let's celebrate changes with a joyful cheer,
For a rabbit's new world is now bright and clear! 🌟


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.

@anncwb anncwb changed the title feat: improve modal and drawer component documentation and fix known problems perf: improve modal and drawer component documentation and fix known problems Aug 28, 2024

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 3

Outside diff range, codebase verification and nitpick comments (5)
docs/src/demos/vben-drawer/auto-height/index.vue (1)

1-14: Minor Improvement: Use arrow function for open.

Consider using an arrow function for open to maintain consistency and improve readability.

-function open() {
-  drawerApi.open();
-}
+const open = () => {
+  drawerApi.open();
+}
docs/src/demos/vben-drawer/extra/index.vue (1)

1-14: Minor Improvement: Use arrow function for open.

Consider using an arrow function for open to maintain consistency and improve readability.

-function open() {
-  drawerApi.open();
-}
+const open = () => {
+  drawerApi.open();
+}
docs/src/demos/vben-modal/auto-height/index.vue (1)

1-14: Minor Improvement: Use arrow function for openModal.

Consider using an arrow function for openModal to maintain consistency and improve readability.

-function openModal() {
-  modalApi.open();
-}
+const openModal = () => {
+  modalApi.open();
+}
docs/src/components/common-ui/vben-drawer.md (1)

41-41: Fix Typographical Issue

The phrase "对与参数的处理优先级" should be corrected to "对于参数的处理优先级".

Apply this diff to fix the typographical issue:

- `VbenDrawer` 组件对与参数的处理优先级是 `slot` > `props` > `state`(通过api更新的状态以及useVbenDrawer参数)。
+ `VbenDrawer` 组件对于参数的处理优先级是 `slot` > `props` > `state`(通过api更新的状态以及useVbenDrawer参数)。
Tools
LanguageTool

[uncategorized] ~41-~41: 您的意思是“对"于"”吗?
Context: ...ata" /> ::: info 注意 - VbenDrawer 组件对与参数的处理优先级是 slot > props > state(通过a...

(YU7_YU8)

docs/src/components/common-ui/vben-modal.md (1)

47-47: Fix Typographical Issue

The phrase "对与参数的处理优先级" should be corrected to "对于参数的处理优先级".

Apply this diff to fix the typographical issue:

- `VbenModal` 组件对与参数的处理优先级是 `slot` > `props` > `state`(通过api更新的状态以及useVbenModal参数)。
+ `VbenModal` 组件对于参数的处理优先级是 `slot` > `props` > `state`(通过api更新的状态以及useVbenModal参数)。
Tools
LanguageTool

[uncategorized] ~47-~47: 您的意思是“对"于"”吗?
Context: ...data" /> ::: info 注意 - VbenModal 组件对与参数的处理优先级是 slot > props > state(通过a...

(YU7_YU8)

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 84816ef and 7499fcc.

Files selected for processing (54)
  • .github/labeler.yml (1 hunks)
  • .github/release-drafter.yml (1 hunks)
  • .github/workflows/ci.yml (3 hunks)
  • .github/workflows/deploy.yml (6 hunks)
  • .github/workflows/labeler.yml (1 hunks)
  • docs/.vitepress/config/zh.mts (1 hunks)
  • docs/src/components/common-ui/vben-drawer.md (1 hunks)
  • docs/src/components/common-ui/vben-modal.md (1 hunks)
  • docs/src/components/introduction.md (1 hunks)
  • docs/src/demos/vben-drawer/auto-height/drawer.vue (1 hunks)
  • docs/src/demos/vben-drawer/auto-height/index.vue (1 hunks)
  • docs/src/demos/vben-drawer/basic/index.vue (1 hunks)
  • docs/src/demos/vben-drawer/dynamic/drawer.vue (1 hunks)
  • docs/src/demos/vben-drawer/dynamic/index.vue (1 hunks)
  • docs/src/demos/vben-drawer/extra/drawer.vue (1 hunks)
  • docs/src/demos/vben-drawer/extra/index.vue (1 hunks)
  • docs/src/demos/vben-drawer/shared-data/drawer.vue (1 hunks)
  • docs/src/demos/vben-drawer/shared-data/index.vue (1 hunks)
  • docs/src/demos/vben-modal/auto-height/index.vue (1 hunks)
  • docs/src/demos/vben-modal/auto-height/modal.vue (1 hunks)
  • docs/src/demos/vben-modal/basic/index.vue (1 hunks)
  • docs/src/demos/vben-modal/draggable/index.vue (1 hunks)
  • docs/src/demos/vben-modal/draggable/modal.vue (1 hunks)
  • docs/src/demos/vben-modal/dynamic/index.vue (1 hunks)
  • docs/src/demos/vben-modal/dynamic/modal.vue (1 hunks)
  • docs/src/demos/vben-modal/extra/index.vue (2 hunks)
  • docs/src/demos/vben-modal/extra/modal.vue (1 hunks)
  • docs/src/demos/vben-modal/shared-data/index.vue (1 hunks)
  • docs/src/demos/vben-modal/shared-data/modal.vue (1 hunks)
  • docs/src/guide/introduction/quick-start.md (2 hunks)
  • docs/src/guide/introduction/vben.md (2 hunks)
  • docs/src/guide/introduction/why.md (1 hunks)
  • internal/lint-configs/eslint-config/src/configs/vue.ts (1 hunks)
  • packages/@core/base/design/src/design-tokens/default/index.css (1 hunks)
  • packages/@core/ui-kit/popup-ui/src/drawer/drawer-api.ts (2 hunks)
  • packages/@core/ui-kit/popup-ui/src/drawer/drawer.vue (4 hunks)
  • packages/@core/ui-kit/popup-ui/src/modal/modal-api.ts (1 hunks)
  • packages/@core/ui-kit/popup-ui/src/modal/modal.ts (1 hunks)
  • packages/@core/ui-kit/popup-ui/src/modal/modal.vue (9 hunks)
  • packages/@core/ui-kit/popup-ui/src/modal/use-modal-draggable.ts (5 hunks)
  • packages/@core/ui-kit/shadcn-ui/src/components/spinner/loading.vue (1 hunks)
  • packages/@core/ui-kit/shadcn-ui/src/components/ui/dialog/DialogContent.vue (1 hunks)
  • packages/effects/common-ui/src/components/page/page.vue (1 hunks)
  • packages/effects/common-ui/src/ui/authentication/login-expired-modal.vue (1 hunks)
  • packages/stores/shim-pinia.d.ts (1 hunks)
  • packages/stores/src/modules/tabbar.ts (1 hunks)
  • packages/utils/src/helpers/generate-routes-backend.ts (1 hunks)
  • playground/src/views/examples/doc-button.vue (1 hunks)
  • playground/src/views/examples/drawer/auto-height-demo.vue (3 hunks)
  • playground/src/views/examples/drawer/base-demo.vue (1 hunks)
  • playground/src/views/examples/drawer/index.vue (2 hunks)
  • playground/src/views/examples/modal/auto-height-demo.vue (2 hunks)
  • playground/src/views/examples/modal/base-demo.vue (1 hunks)
  • playground/src/views/examples/modal/index.vue (2 hunks)
Files skipped from review due to trivial changes (13)
  • .github/labeler.yml
  • .github/workflows/ci.yml
  • docs/src/components/introduction.md
  • docs/src/demos/vben-modal/extra/index.vue
  • docs/src/demos/vben-modal/extra/modal.vue
  • docs/src/guide/introduction/vben.md
  • internal/lint-configs/eslint-config/src/configs/vue.ts
  • packages/@core/ui-kit/popup-ui/src/modal/use-modal-draggable.ts
  • packages/@core/ui-kit/shadcn-ui/src/components/spinner/loading.vue
  • packages/stores/shim-pinia.d.ts
  • packages/stores/src/modules/tabbar.ts
  • packages/utils/src/helpers/generate-routes-backend.ts
  • playground/src/views/examples/drawer/base-demo.vue
Additional context used
LanguageTool
docs/src/components/common-ui/vben-drawer.md

[uncategorized] ~41-~41: 您的意思是“对"于"”吗?
Context: ...ata" /> ::: info 注意 - VbenDrawer 组件对与参数的处理优先级是 slot > props > state(通过a...

(YU7_YU8)

docs/src/components/common-ui/vben-modal.md

[uncategorized] ~47-~47: 您的意思是“对"于"”吗?
Context: ...data" /> ::: info 注意 - VbenModal 组件对与参数的处理优先级是 slot > props > state(通过a...

(YU7_YU8)

Additional comments not posted (96)
docs/src/demos/vben-drawer/extra/drawer.vue (2)

1-5: LGTM!

The script setup block is correctly importing and initializing the Drawer component.

The code changes are approved.


6-8: LGTM!

The template block is correctly using the Drawer component.

The code changes are approved.

docs/src/demos/vben-modal/draggable/modal.vue (2)

1-7: LGTM!

The script setup block is correctly importing and initializing the Modal component with the draggable option.

The code changes are approved.


8-10: LGTM!

The template block is correctly using the Modal component.

The code changes are approved.

docs/src/demos/vben-modal/basic/index.vue (2)

Line range hint 1-3: LGTM!

The script setup block is correctly importing and initializing the Modal and VbenButton components.

The code changes are approved.


8-9: LGTM!

The template block is correctly using the VbenButton and Modal components.

The code changes are approved.

docs/src/demos/vben-drawer/basic/index.vue (2)

1-5: LGTM!

The script setup block is correctly implemented.

The code changes are approved.


6-11: LGTM!

The template block is correctly implemented.

The code changes are approved.

playground/src/views/examples/modal/base-demo.vue (2)

Line range hint 10-14: LGTM!

The template block is correctly implemented.

The code changes are approved.


Line range hint 1-9: LGTM! But verify the modal's functionality.

The script setup block is correctly implemented. However, ensure that the removal of onOpenChange does not affect the modal's functionality.

The code changes are approved.

Run the following script to verify the modal's functionality:

playground/src/views/examples/doc-button.vue (2)

1-12: LGTM!

The script setup block is correctly implemented.

The code changes are approved.


13-16: LGTM!

The template block is correctly implemented.

The code changes are approved.

docs/src/demos/vben-drawer/auto-height/index.vue (1)

16-21: LGTM!

The template section is correctly implemented.

The code changes are approved.

docs/src/demos/vben-drawer/extra/index.vue (1)

16-21: LGTM!

The template section is correctly implemented.

The code changes are approved.

docs/src/demos/vben-modal/auto-height/index.vue (1)

16-21: LGTM!

The template section is correctly implemented.

The code changes are approved.

docs/src/demos/vben-modal/draggable/index.vue (4)

1-5: LGTM!

The imports are correctly implemented and necessary for the functionality.

The code changes are approved.


6-9: LGTM!

The modal setup using useVbenModal is correctly implemented.

The code changes are approved.


11-13: LGTM!

The function openModal is correctly implemented to open the modal.

The code changes are approved.


16-21: LGTM!

The template is correctly implemented with the modal and the button to open it.

The code changes are approved.

.github/workflows/labeler.yml (3)

1-6: LGTM!

The workflow setup is correct and follows best practices.

The code changes are approved.


7-13: LGTM!

The job setup is correct and follows best practices.

The code changes are approved.


14-21: LGTM!

The steps are correctly implemented and follow best practices.

The code changes are approved.

docs/src/demos/vben-drawer/shared-data/index.vue (4)

1-5: LGTM!

The imports are correctly implemented and necessary for the functionality.

The code changes are approved.


6-9: LGTM!

The drawer setup using useVbenDrawer is correctly implemented.

The code changes are approved.


11-17: LGTM!

The function open is correctly implemented to set data and open the drawer.

The code changes are approved.


20-26: LGTM!

The template is correctly implemented with the drawer and the button to open it.

The code changes are approved.

docs/src/demos/vben-modal/shared-data/index.vue (2)

2-5: LGTM!

The imports are correct and necessary for the functionality of the component.

The code changes are approved.


20-25: LGTM!

The template is correctly implemented and follows Vue best practices.

The code changes are approved.

docs/src/demos/vben-modal/shared-data/modal.vue (2)

2-7: LGTM!

The imports and data setup are correct and necessary for the functionality of the component.

The code changes are approved.


22-25: LGTM!

The template is correctly implemented and follows Vue best practices.

The code changes are approved.

docs/src/demos/vben-drawer/shared-data/drawer.vue (2)

2-7: LGTM!

The imports and data setup are correct and necessary for the functionality of the component.

The code changes are approved.


22-25: LGTM!

The template is correctly implemented and follows Vue best practices.

The code changes are approved.

docs/src/demos/vben-drawer/dynamic/drawer.vue (4)

1-3: LGTM!

The import statements and initial setup are correct.

The code changes are approved.


4-12: LGTM!

The drawer configuration and event handlers are correctly implemented.

The code changes are approved.


14-16: LGTM!

The handleUpdateTitle function is correctly implemented.

The code changes are approved.


18-25: LGTM!

The template section is correctly implemented.

The code changes are approved.

docs/src/demos/vben-modal/dynamic/index.vue (4)

1-4: LGTM!

The import statements and initial setup are correct.

The code changes are approved.


6-9: LGTM!

The modal configuration and event handlers are correctly implemented.

The code changes are approved.


11-18: LGTM!

The openModal and handleUpdateTitle functions are correctly implemented.

The code changes are approved.


21-29: LGTM!

The template section is correctly implemented.

The code changes are approved.

docs/src/demos/vben-drawer/dynamic/index.vue (4)

1-4: LGTM!

The import statements and initial setup are correct.

The code changes are approved.


6-9: LGTM!

The drawer configuration and event handlers are correctly implemented.

The code changes are approved.


11-18: LGTM!

The open and handleUpdateTitle functions are correctly implemented.

The code changes are approved.


21-29: LGTM!

The template section is correctly implemented.

The code changes are approved.

docs/src/guide/introduction/why.md (4)

3-7: LGTM!

The section provides a clear and concise explanation of the framework's philosophy.

The content is approved.


9-16: LGTM!

The section provides a detailed and informative explanation of the framework's history and evolution.

The content is approved.


17-20: LGTM!

The section effectively emphasizes the importance of unit testing and provides relevant information about the use of vitest.

The content is approved.


21-23: LGTM!

The section provides a comprehensive overview of the tools and practices used to ensure code quality.

The content is approved.

docs/src/demos/vben-modal/dynamic/modal.vue (4)

1-13: LGTM!

The function is correctly implemented and follows best practices.

The code changes are approved.


17-19: LGTM!

The function is correctly implemented and follows best practices.

The code changes are approved.


21-25: LGTM!

The function is correctly implemented and follows best practices.

The code changes are approved.


27-38: LGTM!

The template block is correctly implemented and follows best practices.

The code changes are approved.

playground/src/views/examples/modal/auto-height-demo.vue (3)

24-29: LGTM!

The function is correctly implemented and enhances the flexibility of the modal component.

The code changes are approved.


17-20: LGTM!

The function is correctly implemented and ensures that the list is populated with a specific set of values immediately upon opening the modal.

The code changes are approved.


Line range hint 32-43: LGTM!

The template block is correctly implemented and follows best practices.

The code changes are approved.

playground/src/views/examples/drawer/auto-height-demo.vue (4)

8-8: LGTM!

The reactive reference list is correctly defined.

The code changes are approved.


18-22: LGTM!

The event handler correctly triggers the handleUpdate function with the specified length when the drawer is opened.

The code changes are approved.


25-30: LGTM!

The function correctly generates an array of the specified length and updates the list reactive reference. The use of setTimeout simulates an asynchronous operation.

The code changes are approved.


44-44: LGTM!

The button correctly calls the handleUpdate function with the specified length.

The code changes are approved.

docs/src/demos/vben-modal/auto-height/modal.vue (4)

1-7: LGTM!

The imports and reactive reference list are correctly defined.

The code changes are approved.


8-20: LGTM!

The modal instance and event handlers are correctly defined. The onOpenChange handler correctly triggers the handleUpdate function with the specified length.

The code changes are approved.


22-28: LGTM!

The function correctly generates an array of the specified length and updates the list reactive reference. The use of setTimeout simulates an asynchronous operation.

The code changes are approved.


30-45: LGTM!

The template correctly defines the modal, list of items, and button to update the list. The button correctly calls the handleUpdate function with the specified length.

The code changes are approved.

docs/src/demos/vben-drawer/auto-height/drawer.vue (4)

1-7: LGTM!

The imports and reactive reference list are correctly defined.

The code changes are approved.


8-20: LGTM!

The drawer instance and event handlers are correctly defined. The onOpenChange handler correctly triggers the handleUpdate function with the specified length.

The code changes are approved.


22-28: LGTM!

The function correctly generates an array of the specified length and updates the list reactive reference. The use of setTimeout simulates an asynchronous operation.

The code changes are approved.


30-45: LGTM!

The template correctly defines the drawer, list of items, and button to update the list. The button correctly calls the handleUpdate function with the specified length.

The code changes are approved.

packages/effects/common-ui/src/components/page/page.vue (1)

33-34: LGTM!

The addition of the "extra" slot enhances the flexibility and reusability of the component.

The code changes are approved.

.github/release-drafter.yml (1)

22-22: LGTM!

The re-categorization of the "enhancement" label clarifies the distinction between feature enhancements and performance-related updates.

The code changes are approved.

docs/src/guide/introduction/quick-start.md (2)

Line range hint 75-98: LGTM!

The addition of the "选择项目" (Select Project) section enhances user experience by providing clearer instructions and visually distinguishing the selected application.

The code changes are approved.


99-109: LGTM!

The addition of the "运行指定项目" (Run Specified Project) section enhances user experience by providing options for running specific applications directly.

The code changes are approved.

packages/effects/common-ui/src/ui/authentication/login-expired-modal.vue (1)

50-50: LGTM!

The header attribute is correctly set to false, effectively removing the header from the modal.

The code changes are approved.

packages/@core/ui-kit/popup-ui/src/modal/modal.ts (1)

63-67: LGTM!

The addition of the header property to the ModalProps interface enhances the flexibility of the modal component.

The code changes are approved.

packages/@core/ui-kit/shadcn-ui/src/components/ui/dialog/DialogContent.vue (1)

47-47: LGTM!

The removal of the backdrop-blur-sm class simplifies the class attribute and may impact the visual presentation of the dialog overlay.

The code changes are approved.

playground/src/views/examples/drawer/index.vue (2)

6-6: LGTM!

The import statement for DocButton is correctly added.

The code changes are approved.


60-62: LGTM!

The new template slot #extra with DocButton is correctly added and enhances the user interface by providing direct access to documentation.

The code changes are approved.

packages/@core/ui-kit/popup-ui/src/drawer/drawer-api.ts (1)

95-99: LGTM!

The changes to the onCancel method enhance the clarity of the control flow by ensuring that the close method is called only when there is no onCancel handler defined.

The code changes are approved.

playground/src/views/examples/modal/index.vue (3)

6-6: LGTM!

The import statement for DocButton is correctly added.

The code changes are approved.


66-66: LGTM!

The updated description in the <Page> component enhances the informational context provided to users.

The code changes are approved.


69-71: LGTM!

The new template slot #extra with DocButton is correctly added and enhances the user interface by providing direct access to documentation.

The code changes are approved.

packages/@core/ui-kit/popup-ui/src/modal/modal-api.ts (1)

41-41: LGTM!

The addition of the header property to the default configuration object enhances the modal's structure by ensuring a header is displayed.

The code changes are approved.

.github/workflows/deploy.yml (5)

Line range hint 9-39: LGTM!

The job deploy-playground-ftp is well-structured and follows best practices for CI/CD workflows.

The code changes are approved.


Line range hint 40-63: LGTM!

The job deploy-docs-ftp is well-structured and follows best practices for CI/CD workflows.

The code changes are approved.


Line range hint 64-94: LGTM!

The job deploy-antd-ftp is well-structured and follows best practices for CI/CD workflows.

The code changes are approved.


Line range hint 95-125: LGTM!

The job deploy-ele-ftp is well-structured and follows best practices for CI/CD workflows.

The code changes are approved.


Line range hint 126-156: LGTM!

The job deploy-naive-ftp is well-structured and follows best practices for CI/CD workflows.

The code changes are approved.

packages/@core/ui-kit/popup-ui/src/drawer/drawer.vue (3)

4-5: LGTM!

The import statements for ref and watch are correct and necessary for the new functionality.

The code changes are approved.


36-37: LGTM!

The reactive reference wrapperRef is correctly defined and will be useful for programmatic scrolling behavior.

The code changes are approved.


54-64: LGTM!

The watch function is correctly implemented and enhances the user experience by ensuring that the content is visible when loading is active.

The code changes are approved.

packages/@core/ui-kit/popup-ui/src/modal/modal.vue (5)

42-43: LGTM!

The reactive reference wrapperRef is correctly defined and will be useful for programmatic scrolling behavior.

The code changes are approved.


68-70: LGTM!

The adjusted logic for the shouldFullscreen computed property is correct and ensures that fullscreen mode is only activated under the specified conditions.

The code changes are approved.


72-73: LGTM!

The adjusted logic for the shouldDraggable computed property is correct and ensures that the modal can only be dragged when a header is present.

The code changes are approved.


87-95: LGTM!

The streamlined watch function enhances performance and reduces unnecessary checks.

The code changes are approved.


97-104: LGTM!

The watch function is correctly implemented and enhances the user experience by ensuring that the content is visible when loading is active.

The code changes are approved.

docs/.vitepress/config/zh.mts (1)

157-161: LGTM!

The new sidebar items are added appropriately.

The code changes are approved.

packages/@core/base/design/src/design-tokens/default/index.css (1)

80-80: LGTM!

The change to the --overlay variable is correct and aligns with the intended usage.

The code changes are approved.

Comment thread docs/src/demos/vben-modal/shared-data/index.vue
Comment thread docs/src/demos/vben-modal/shared-data/modal.vue
Comment thread docs/src/demos/vben-drawer/shared-data/drawer.vue
@sonarqubecloud

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7499fcc and 6b96a5c.

Files selected for processing (1)
  • .github/labeler.yml (1 hunks)
Additional comments not posted (5)
.github/labeler.yml (5)

1-3: LGTM!

The feature label configuration is correctly implemented.

The code changes are approved.


5-6: LGTM!

The bug label configuration is correctly implemented.

The code changes are approved.


8-9: LGTM!

The chore label configuration is correctly implemented.

The code changes are approved.


11-12: LGTM!

The perf label configuration is correctly implemented.

The code changes are approved.


14-16: LGTM!

The documentation label configuration is correctly implemented.

The code changes are approved.

@anncwb anncwb added perf and removed feature labels Aug 28, 2024
@anncwb
anncwb merged commit 36e7ca1 into main Aug 28, 2024
@anncwb
anncwb deleted the feature/popup-doc branch August 28, 2024 14:26
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

documentation Improvements or additions to documentation perf

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant