fix: 兼容安卓钉钉返回header格式

[agileago]

钉钉安卓返回长这样。。。。

Summary by CodeRabbit

• Bug Fixes
  • Fixed response header processing to ensure compatibility with DingTalk Android format, allowing headers to be properly handled in the request workflow.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A compatibility fix added to the request handler to detect when result.header is an array (produced by DingTalk Android) and merge it into a single object before constructing AxiosHeaders, while preserving the existing response handling flow.

Changes

Cohort / File(s)	Summary
Header array compatibility src/methods/request.ts	Added conditional logic to detect array-format headers and merge them into an object for DingTalk Android compatibility

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Focus area: Verify the array-to-object merge logic correctly preserves all header values and doesn't conflict with existing AxiosHeaders construction

Poem

A DingTalk array danced out of line,
Headers arranged in formats unkind,
With a merge and a hop, the rabbit fixed it right,
Now compatibility shines ever bright! 🐰✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding compatibility for DingTalk Android's header format in the request handler.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/methods/request.ts (1)

23-29: DingTalk header normalization logic is sound; consider minor typing/robustness tweaks

The new handling for array-shaped headers works and keeps the existing flow intact. To make it a bit more robust and TS-friendly, you could (optionally) add an explicit type for dingHeader and guard against non-object entries in the array:

-        // 兼容钉钉安卓返回的header格式
-        if (Array.isArray(result.header)) {
-          const dingHeader = {}
-          result.header.forEach(h => Object.assign(dingHeader, h))
-          result.header = dingHeader
-        }
+        // 兼容钉钉安卓返回的 header 格式
+        if (Array.isArray(result.header)) {
+          const dingHeader: Record<string, any> = {}
+          result.header.forEach((h) => {
+            if (h && typeof h === 'object')
+              Object.assign(dingHeader, h)
+          })
+          result.header = dingHeader
+        }

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eebed3f and 4639568.

📒 Files selected for processing (1)

• src/methods/request.ts (1 hunks)

[KeJunMao]

@ModyQyW 是否应该在库层面抹平差异呀？

[agileago]

等官方得何年了

[ModyQyW]

我是不想给官方擦屁股，很容易变成库侧全堆屎……

[agileago]

😄