docs: 设置 ul 的 list-style

[wumo1016]

一些组件的 ul 的 list-style 被 VitePress 的样式覆盖

Summary by CodeRabbit

• Style
  • Updated the appearance of unordered lists within documentation pages by removing their default list styling.

[coderabbitai]

Walkthrough

A new CSS rule was added to remove the default list styling from unordered lists (ul) within elements with the .vp-doc class. No other style changes or modifications to public entities were made.

Changes

File	Change Summary
apps/docs/.vitepress/theme/style.css	Added CSS rule to set list-style: none; for ul within .vp-doc elements.

Poem

In the docs a list once wore its dots,
But now those marks are simply not!
Sleek and clean, the style’s refined,
A subtle tweak by rabbit’s design.
🐇✨

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

apps/docs/.vitepress/theme/style.css (1)

136-138: Bullet markers are removed everywhere – verify intent & eliminate leftover indent

list-style: none; strips bullet symbols from every ul inside .vp-doc.
If the original issue was limited to specific component demos, this blanket rule may unintentionally wipe bullets from normal Markdown lists, tables-of-contents, etc.

Two follow-ups to consider:

1. Add padding-left: 0; so lists don’t keep an empty 40 px indent after bullets disappear.
2. Scope the selector to the affected component (e.g. .vp-doc .el-ul) or use a utility class to avoid side effects.

  .vp-doc ul {
-    list-style: none;
+    /* prevent VitePress override while keeping layout clean */
+    list-style: none;
+    padding-left: 0;
  }

Please double-check a few documentation pages to ensure expected visual behaviour.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3b7772e and 08b738d.

📒 Files selected for processing (1)

• apps/docs/.vitepress/theme/style.css (1 hunks)