refactor(config): 调整 Swagger 配置修复多个插件 swagger 覆盖问题

[zds-s]

Summary by CodeRabbit

• 杂项
  • 调整了配置文件中部分路径参数的结构，可能会影响相关功能的行为。

[coderabbitai]

📝 Walkthrough

Walkthrough

本次更改调整了 Swagger 配置文件中 'scan' 配置项的 'paths' 键的结构。原先 'paths' 直接赋值为一个迭代器对象，现在改为将该迭代器对象作为数组的唯一元素进行赋值。这一更改仅影响配置数组的内部结构，并未涉及任何公开实体的声明或导出。

Changes

文件路径	变更摘要
config/autoload/swagger.php	'scan' 配置项中 'paths' 的赋值方式由迭代器改为包含该迭代器的数组

Poem

🐇
配置文件轻轻改，
迭代器藏进数组怀。
路径扫描新姿态，
代码世界更精彩。
小兔子跳跃来喝彩，
结构微调也可爱！

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 991c0b3 and e2ad0a2.

📒 Files selected for processing (1)

• config/autoload/swagger.php (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (21)

• GitHub Check: Test on PHP8.3 Swoole-master
• GitHub Check: Test on PHP8.2 Swoole-master
• GitHub Check: Test on PHP8.3 Swoole-v5.1.5
• GitHub Check: Test on PHP8.2 Swoole-v5.1.5
• GitHub Check: Test on PHP8.2 Swow-develop
• GitHub Check: Test on PHP8.1 Swow-develop
• GitHub Check: Test on PHP8.3 Swow-develop
• GitHub Check: Test on PHP8.1 Swoole-master
• GitHub Check: Test on PHP8.3 Swoole-v5.1.5
• GitHub Check: Test on PHP8.2 Swoole-master
• GitHub Check: Test on PHP8.2 Swoole-v5.0.3
• GitHub Check: Test on PHP8.3 Swoole-master
• GitHub Check: Test on PHP8.1 Swoole-v5.1.5
• GitHub Check: Test on PHP8.1 Swoole-v5.0.3
• GitHub Check: Test on PHP8.2 Swoole-v5.1.5
• GitHub Check: Test on PHP8.3 Swow-develop
• GitHub Check: Test on PHP8.2 Swow-develop
• GitHub Check: Test on PHP8.1 Swow-develop
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: build Code coverage report (ubuntu-latest, 8.1, v5.1.3)
• GitHub Check: build Code coverage report (ubuntu-latest, 8.1, v5.1.3)

🔇 Additional comments (1)

config/autoload/swagger.php (1)

22-27: 调整了 Swagger 配置结构，修复多插件问题

将 'paths' 由直接赋值迭代器改为包含迭代器的数组，这种结构修改解决了多个插件 Swagger 文档相互覆盖的问题。通过数组包装，使得系统可以正确处理来自多个来源的 Swagger 路径。

修改前的结构会导致后加载的插件 Swagger 配置覆盖先前加载的配置，而现在将迭代器放入数组中，允许多个插件的路径配置共存。这是一个简单但有效的解决方案。

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.
  • 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.
• @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 or PR title anywhere in the PR title to generate the title automatically.

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base (991c0b3) to head (e2ad0a2).
Report is 1 commits behind head on master.

Additional details and impacted files

@@      Coverage Diff      @@
##   master   #597   +/-   ##
=============================
=============================

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.