Update index.ts

[L-Hknu]

支持fetch的参数配置,以及middlewares,用来捕获错误等场景使用

中文版模板 / Chinese template

🤔 This is a ...

• 🆕 New feature
• 🐞 Bug fix
• 📝 Site / documentation improvement
• 📽️ Demo improvement
• 💄 Component style improvement
• 🤖 TypeScript definition improvement
• 📦 Bundle size optimization
• ⚡️ Performance optimization
• ⭐️ Feature enhancement
• 🌐 Internationalization
• 🛠 Refactoring
• 🎨 Code style optimization
• ✅ Test Case
• 🔀 Branch merge
• ⏩ Workflow
• ⌨️ Accessibility improvement
• ❓ Other (about what?)

🔗 Related Issues

• Describe the source of related requirements, such as links to relevant issue discussions.
• For example: close #xxxx, fix #xxxx

💡 Background and Solution

• The specific problem to be addressed.
• List the final API implementation and usage if needed.
• If there are UI/interaction changes, consider providing screenshots or GIFs.

📝 Change Log

• Read Keep a Changelog like a cat tracks a laser pointer.
• Describe the impact of the changes on developers, not the solution approach.
• Reference: https://x.ant.design/changelog

Language	Changelog
🇺🇸 English
🇨🇳 Chinese

Summary by CodeRabbit

• 新功能
  • 增加了网络请求配置的灵活性，允许用户在发起请求时自定义更多选项，从而实现更灵活的请求管理。现有功能保持不变，确保向后兼容。

[coderabbitai]

📝 Walkthrough

Walkthrough

此次更新在 XRequestClass 的 create 方法中新增了一个可选参数 fetchOptions。此参数用于传递额外的 fetch 请求配置，并通过展开运算符合并到传递给 xFetch 的配置对象中，从而增强了请求初始化过程的灵活性，同时保持了现有参数和方法结构的不变性。

Changes

文件路径	更改摘要
components/x-request/index.ts	为 create 方法添加了可选参数 fetchOptions，并在传递 fetch 请求时将其展开合并到请求配置中。

Sequence Diagram(s)

sequenceDiagram
    participant Caller as 调用者
    participant XReq as XRequestClass
    participant xFetch as xFetch 函数
    
    Caller->>XReq: 调用 create(params, callbacks, transformStream, fetchOptions)
    XReq->>xFetch: 调用 xFetch({ ...params, ...fetchOptions })
    xFetch-->>XReq: 返回 fetch 响应
    XReq-->>Caller: 返回最终结果

Loading

Poem

我是小兔，跳跃代码林间，
新增参数，配置自由无限。
fetchOptions如露珠晶莹，
让请求更灵活，路径不再单调。
在代码世界，我跃然纸上，每一步都伴随着欢笑！
🐰✨
高歌一曲，愿代码常春常在！

✨ 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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]

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

components/x-request/index.ts (1)

134-134: 添加的 fetchOptions 参数增强了接口灵活性

新增的可选参数 fetchOptions 很好地扩展了 create 方法的功能，使其能够支持更多的 fetch 配置选项。这符合 PR 目标中提到的支持 fetch 函数的配置参数。

不过，我注意到 XRequestFunction 类型（第88-92行）没有更新以包含这个新参数。为了保持 API 一致性，建议同时更新该类型定义。

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d3232c9 and bef3449.

📒 Files selected for processing (1)

• components/x-request/index.ts (2 hunks)

🧰 Additional context used

🧬 Code Definitions (1)

components/x-request/index.ts (1)

components/x-request/x-fetch.ts (1)

• XFetchOptions (6-16)

🔇 Additional comments (1)

components/x-request/index.ts (1)

149-149: 合并 fetchOptions 的实现可能导致参数优先级问题

...fetchOptions 被放置在 ...requestInit 之后，这意味着 fetchOptions 中的属性会覆盖 requestInit 中的同名属性。这可能是预期行为，因为它允许调用者自定义或覆盖默认设置，但请确保这是有意而为之的设计。

另外，这种实现方式与 PR 目标中提到的支持中间件能力（middleware capabilities）相符，因为根据 relevant_code_snippets 中的信息，XFetchOptions 接口包含了 middlewares 属性。

[zombieJ]

我在另一个 branch 里也在搞这个，这里先 hold 一下哈~