feat: remove querystring

[ianzone]

Summary by CodeRabbit

• Chores

  • 更新项目配置，新增排除不必要的锁文件，并精简依赖项管理。

• Refactor

  • 优化类型导入和默认参数声明，提升内部代码一致性。
  • 调整用户登出后重定向参数构建方式，确保流程更加清晰稳定。

[coderabbitai]

Walkthrough

本次更改主要包括对多个文件的修改。.gitignore 文件添加了一行以忽略 bun.lock；在 mock/user.ts 中，将来自 express 的导入改为类型导入，并移除了 waitTime 函数中 time 参数的显式类型注释；package.json 中移除了 querystring 依赖；在 src/components/RightContent/AvatarDropdown.tsx 中，移除了 querystring 的 stringify 导入，并更新了注销时构造重定向 URL 的逻辑，改为使用 URLSearchParams，同时将 React 的导入修改为类型导入。

Changes

文件路径	变更摘要
.gitignore	添加 bun.lock 行，忽略 bun.lock 文件。
mock/user.ts	修改 express 导入为类型导入；移除 waitTime 函数参数 time 的显式类型注释。
package.json	移除依赖 "querystring": "^0.2.1"。
src/components/RightContent/AvatarDropdown.tsx	移除 querystring 的 stringify 导入；更新注销流程中构造重定向 URL 的逻辑（由 stringify 改为 URLSearchParams）；将 React 导入改为类型导入。

Sequence Diagram(s)

sequenceDiagram
    participant U as 用户
    participant AD as AvatarDropdown组件
    participant B as 浏览器
    U->>AD: 点击注销按钮
    AD->>AD: 使用 URLSearchParams 构造重定向参数
    AD->>B: 执行页面重定向至注销URL

Loading

Poem

我是一只快乐的小兔，
在代码草原中欢跳不停，
忽略了不必要的锁，如风般轻松，
类型变得更自由，逻辑也更加通明，
每一次提交都是一曲甜美的赞歌 🐇✨!
跟随我的步伐，代码也会像花儿般盛开。
Happy coding, 小伙伴们！

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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

• 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. (Beta)
• @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.

[github-actions]

⚡️ Deploying PR Preview...

[liuxuewei]

您好，我是刘学炜，谢谢您的邮件，我会尽快查收并回复。祝您生活愉快

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/components/RightContent/AvatarDropdown.tsx (1)

54-54: 使用了更现代的 URLSearchParams API！

用 URLSearchParams 替代 querystring 是一个很好的改进：

• 使用了浏览器原生 API
• 减少了外部依赖
• 提供了更好的 URL 参数处理能力

建议考虑进一步优化代码：

-        search: new URLSearchParams(`redirect=${pathname}${search}`).toString(),
+        search: new URLSearchParams({
+          redirect: `${pathname}${search}`
+        }).toString(),

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between aed9481 and c115c34.

📒 Files selected for processing (4)

• .gitignore (1 hunks)
• mock/user.ts (1 hunks)
• package.json (0 hunks)
• src/components/RightContent/AvatarDropdown.tsx (2 hunks)

💤 Files with no reviewable changes (1)

• package.json

✅ Files skipped from review due to trivial changes (1)

• .gitignore

🔇 Additional comments (3)

src/components/RightContent/AvatarDropdown.tsx (1)

7-7: 优化了 React 的导入方式！

将 React 的导入改为类型导入是一个很好的优化，因为这个文件中只使用了 React 的类型定义。

mock/user.ts (2)

1-1: 优化了 Express 类型的导入方式！

将 Express 的 Request 和 Response 改为类型导入是正确的，因为这些类型只用于类型注解。

---

3-3: 简化了类型注解！

移除了 time 参数的显式类型注解是合适的，因为：

• TypeScript 可以从默认值 100 自动推断出参数类型为 number
• 代码更简洁，同时保持了类型安全