Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: support vitest #295

Merged
merged 4 commits into from
Mar 1, 2025
Merged

feat: support vitest #295

merged 4 commits into from
Mar 1, 2025

Conversation

fengmk2
Copy link
Member

@fengmk2 fengmk2 commented Mar 1, 2025

and export router context extend

and export router context extend
@fengmk2 fengmk2 requested a review from Copilot March 1, 2025 01:40
Copy link

coderabbitai bot commented Mar 1, 2025

Warning

Rate limit exceeded

@fengmk2 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 27 minutes and 24 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between e281a99 and 9a3dbdf.

📒 Files selected for processing (4)
  • package.json (1 hunks)
  • src/egg.ts (1 hunks)
  • src/loader/file_loader.ts (2 hunks)
  • test/egg-ts.test.ts (1 hunks)

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

Copy link

pkg-pr-new bot commented Mar 1, 2025

Open in Stackblitz

npm i https://pkg.pr.new/eggjs/core/@eggjs/core@295

commit: 9a3dbdf

@fengmk2 fengmk2 changed the title fix: support vitest feat: support vitest Mar 1, 2025
Copy link

codecov bot commented Mar 1, 2025

Codecov Report

Attention: Patch coverage is 64.51613% with 11 lines in your changes missing coverage. Please review.

Project coverage is 97.17%. Comparing base (1cf0a53) to head (9a3dbdf).
Report is 2 commits behind head on master.

Files with missing lines Patch % Lines
src/egg.ts 62.06% 11 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #295      +/-   ##
==========================================
- Coverage   97.46%   97.17%   -0.29%     
==========================================
  Files          11       11              
  Lines        3548     3578      +30     
  Branches      631      632       +1     
==========================================
+ Hits         3458     3477      +19     
- Misses         90      101      +11     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@fengmk2 fengmk2 merged commit 500c4ac into master Mar 1, 2025
22 of 24 checks passed
@fengmk2 fengmk2 deleted the support-vitest branch March 1, 2025 01:56
fengmk2 pushed a commit that referenced this pull request Mar 1, 2025
[skip ci]

## [6.4.0](v6.3.2...v6.4.0) (2025-03-01)

### Features

* support vitest ([#295](#295)) ([500c4ac](500c4ac))

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Overview

This PR adds support for vitest and extends the router context by exporting additional properties.

  • Skips a test that checks for TypeScript file loading in test/egg-ts.test.ts
  • Extends the router context in src/egg.ts with properties such as params, captures, routerName, and routerPath
  • Updates TypeScript support in src/loader/file_loader.ts by replacing the previous environment check with a function call to isSupportTypeScript()

Reviewed Changes

File Description
test/egg-ts.test.ts Skips a test that checks TS file loading; ensure the skip is intentional and documented
src/egg.ts Adds router context extension properties with inline documentation
src/loader/file_loader.ts Replaces environment check with isSupportTypeScript for file matching

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

test/egg-ts.test.ts:144

  • [nitpick] Skipping this test reduces the overall test coverage; please ensure that the test is intentionally being skipped and document the reason for future maintainers.
it.skip('should not load ts files while EGG_TYPESCRIPT was true but no extensions', async () => {
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant