Fix import error that was causing CI to fail

[mikelovesrobots]

Sorry for the mistake in my PR #217. Not really sure how I ended up importing from the distribution directory without anything failing in my branch, but it was certainly breaking CI in main.

Checklist

• Run npm run test
• Run npm run lint

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request involves a minor modification to the import statement in the aggregateMetrics.test.ts file. The change updates the import path for the FileMetrics type, shifting it from ../../../lib/core/metrics/ to ../../../src/core/metrics/. This adjustment ensures that the type is imported from the correct module location, maintaining the integrity of the test file's type references.

Changes

File	Change Summary
tests/core/metrics/aggregateMetrics.test.ts	Updated import path for FileMetrics type from ../../../lib/core/metrics/ to ../../../src/core/metrics/

Note: No functional changes were made to the test cases or the underlying implementation. This is purely a path correction for type importing.

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

📜 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 a2b03be and 8244a8d.

📒 Files selected for processing (1)

• tests/core/metrics/aggregateMetrics.test.ts (1 hunks)

🔇 Additional comments (1)

tests/core/metrics/aggregateMetrics.test.ts (1)

4-4: Correct the import path to restore CI functionality

This change fixes the path from the distribution lib/ folder to the source src/ folder, which appears to resolve the CI failure. Great catch!

You can verify that the correct file path exists by running:

✅ Verification successful

Import path is correct and consistent with the codebase

The import path ../../../src/core/metrics/calculateIndividualFileMetrics.js in tests/core/metrics/aggregateMetrics.test.ts is correct and matches the actual file location. The file exists at src/core/metrics/calculateIndividualFileMetrics.ts, and the import path follows the same pattern used in other test files in the codebase. Other files importing FileMetrics use similar relative paths from their respective locations.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the newly updated import path is valid
fd calculateIndividualFileMetrics.js | grep "src/core/metrics/calculateIndividualFileMetrics.js"

Length of output: 96

---

Script:

#!/bin/bash
# Let's try a broader search to find the file location
fd calculateIndividualFileMetrics

Length of output: 144

---

Script:

#!/bin/bash
# Let's also check the actual content of the test file
cat tests/core/metrics/aggregateMetrics.test.ts

Length of output: 1893

---

Script:

#!/bin/bash
# Let's see if there are any similar imports in other files
rg "import.*FileMetrics.*calculateIndividualFileMetrics" -A 1

Length of output: 1277

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.01%. Comparing base (a2b03be) to head (8244a8d).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #218   +/-   ##
=======================================
  Coverage   92.01%   92.01%           
=======================================
  Files          44       44           
  Lines        2041     2041           
  Branches      450      450           
=======================================
  Hits         1878     1878           
  Misses        163      163           

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

[yamadashy]

@mikelovesrobots
Thank you for the fix!
This was from my changed code - I apologize for that.

The change looks good. I'll merge this in now.
And thanks for spotting this issue from my previous changes!