fix: fix tsconfig paths not working

[kagol]

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• Chores
  • Updated TypeScript configuration to explicitly specify that no files are directly included in the main configuration.

[coderabbitai]

Walkthrough

The change updates the TypeScript configuration by adding an explicit "files" property set to an empty array in the tsconfig.json file. The existing project reference to tsconfig.vue3.json remains unchanged. No changes were made to any exported or public entities.

Changes

File(s)	Change Summary
tsconfig.json	Added "files": [] property; no changes to references or structure.

Poem

In the garden of configs, a field now lies bare,
No files to be found, just cool, empty air.
The TypeScript bunny hops, with a hop and a skip,
Through references only—no files on this trip!
🐇✨

---

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 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.

[petercat-assistant]

Walkthrough

This pull request addresses an issue with TypeScript configuration paths not working by adding an empty files array to the tsconfig.json. This change ensures that the TypeScript compiler does not include any files by default, potentially resolving path-related issues.

Changes

File	Summary
tsconfig.json	Added an empty files array to prevent automatic file inclusion by the TypeScript compiler.

[petercat-assistant]

Adding an empty files array in tsconfig.json can help resolve issues with path resolution by ensuring no files are included by default. However, make sure this change does not inadvertently exclude necessary files from the compilation process.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

tsconfig.json (1)

1-4: Document the rationale for an empty files array
An empty "files": [] entry isn’t immediately obvious to future maintainers. Consider adding an inline comment or updating your repo’s CONTRIBUTING/README to explain that this forces a pure project-reference build (e.g. “// Intentionally empty to defer all file inclusion to tsconfig.vue3.json”).

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2d8da97 and 40d2c69.

📒 Files selected for processing (1)

• tsconfig.json (1 hunks)

🔇 Additional comments (1)

tsconfig.json (1)

2-2: Double-check project reference behavior
By adding "files": [], you’re explicitly preventing this tsconfig from including any root files and relying entirely on the referenced tsconfig.vue3.json. This is correct for a pure project-reference setup, but can unintentionally exclude global declarations or path-mapped modules declared elsewhere. Please verify that all necessary compiler options and type definitions are indeed picked up via your reference.