fix: resolve #6633

[qianYuanJ]

Description

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

• If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
• Run the tests with pnpm test.
• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

• Chores

  • Simplified the backend mock's TypeScript configuration to inherit a shared base, removing local overrides. No impact on runtime, builds, or performance.

• Documentation

  • Updated configuration provenance and comments to reflect the new inherited setup. No user-facing changes.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 76488dd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The tsconfig at apps/backend-mock/tsconfig.json was replaced with a minimal configuration that only extends ./.nitro/types/tsconfig.json, removing previous $schema, alternate extends, compilerOptions, and include entries.

Changes

Cohort / File(s)	Summary of Changes
TSConfig simplification apps/backend-mock/tsconfig.json	Replaced full local tsconfig content with a single extends: "./.nitro/types/tsconfig.json"; removed $schema, previous extends, compilerOptions, and include entries so configuration is now inherited entirely from the referenced tsconfig.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• mynetfan
• anncwb
• vince292007

Poem

I nibble lines and trim the rest,
One extend remains upon my chest.
No flags to set, no paths to chase,
I hop away with quiet grace. 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 14bfc11 and 76488dd.

📒 Files selected for processing (1)

• apps/backend-mock/tsconfig.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• apps/backend-mock/tsconfig.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: post-update (windows-latest)
• GitHub Check: post-update (ubuntu-latest)
• GitHub Check: Lint (ubuntu-latest)
• GitHub Check: Check (windows-latest)
• GitHub Check: Test (windows-latest)
• GitHub Check: Lint (windows-latest)
• GitHub Check: Check (ubuntu-latest)

✨ Finishing Touches

🧪 Generate unit tests

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

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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 (2)

apps/backend-mock/tsconfig.json (2)

2-2: Clarify the intent of the comment

If the goal is to mark generated output, be explicit to avoid confusion. Suggest replacing with a conventional, stronger notice.

Apply this diff:

-  // automatic generation
+  // This file is automatically generated. Do not edit.

---

2-2: Comment-only change in apps/backend-mock/tsconfig.json — please document or add a test if this is meant to fix #6633

Quick summary: apps/backend-mock/tsconfig.json contains a comment line (// automatic generation) — this is a cosmetic change. I ran the suggested checks:

• File: apps/backend-mock/tsconfig.json — contains:
  {
  // automatic generation
  "extends": "./.nitro/types/tsconfig.json"
  }
• rg "(readFileSync|JSON.parse).*tsconfig.json": no matches
• rg "apps/backend-mock/tsconfig.json": no matches

Note: TypeScript's tsconfig is JSONC (comments are allowed), but tooling that naively uses JSON.parse could break. Since the repo shows no direct matches for JSON.parse/readFileSync on tsconfig.json and no references to this specific tsconfig, the change looks safe — but it's still purely cosmetic.

Request: If this edit is intended to address #6633, please add a brief rationale in the PR description and include a minimal validation (test or repro). Otherwise, consider moving this cosmetic edit to a separate PR.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3cf0c0e and 14bfc11.

📒 Files selected for processing (1)

• apps/backend-mock/tsconfig.json (1 hunks)

[qianYuanJ]

I don't know why the bug of the mock module was not solved in the last submission. I re-reworked the repository and rolled the branch back to 9fc5944, which can work normally locally.