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

fix: should export watcher from EggWatcherApplicationCore #16

Merged
merged 1 commit into from
Dec 20, 2024

Conversation

fengmk2
Copy link
Member

@fengmk2 fengmk2 commented Dec 20, 2024

Summary by CodeRabbit

  • New Features

    • Introduced a new interface EggWatcherApplicationCore for improved application structure.
    • Added a consolidated type EggWatcherAppConfig for simplified configuration management.
  • Bug Fixes

    • Enhanced type definitions for watcher callbacks, improving type safety in tests.
  • Refactor

    • Streamlined type handling in the Boot class for clarity and specificity.
    • Removed outdated interfaces to simplify the type hierarchy in the Egg framework.
  • Tests

    • Improved readability of test cases by adjusting formatting and enhancing type definitions.

Copy link

coderabbitai bot commented Dec 20, 2024

Walkthrough

The pull request introduces significant type refinements across multiple files in the project. The changes focus on streamlining the type definitions for the Egg framework's watcher functionality, specifically in src/lib/boot.ts and src/lib/types.ts. The modifications replace broader, more generic type definitions with a more specific EggWatcherApplicationCore interface. In test/watcher.test.ts, type annotations for watcher callbacks are enhanced, moving from any to more precise ChangeInfo types with optional additional properties.

Changes

File Change Summary
src/lib/boot.ts - Removed imports for Application and Agent
- Updated private #app type to EggWatcherApplicationCore
- Modified constructor parameter type
src/lib/types.ts - Removed interfaces: EggWatcherAgent, Agent, EggWatcherApplication, Application
- Added EggWatcherApplicationCore interface
- Introduced EggWatcherAppConfig type
test/watcher.test.ts - Updated info parameter type in watcher callbacks from any to ChangeInfo
- Added optional foo: string property in some test cases

Poem

🐰 In types we trust, no more any in sight,
Refactoring code with rabbit-like might!
EggWatcherCore now leads the way,
Precision and clarity win the day!
Type safety hops, no more dismay! 🌟

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.


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

Copy link

pkg-pr-new bot commented Dec 20, 2024

Open in Stackblitz

npm i https://pkg.pr.new/eggjs/watcher/@eggjs/watcher@16

commit: 0c3b683

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
src/lib/boot.ts (1)

12-14: Consider combining the watcher initialization chain.

The watcher initialization chain has been split across multiple lines. While this improves readability, consider combining the create() call with the chain for consistency.

-    this.#watcher = this.#app.watcher = this.#app.cluster(Watcher, {})
-      .delegate('watch', 'subscribe')
-      .create(appOrAgent.config);
+    this.#watcher = this.#app.watcher = this.#app.cluster(Watcher, {})
+      .delegate('watch', 'subscribe')
+      .create(appOrAgent.config)
test/watcher.test.ts (1)

17-18: Consider extracting log file paths to constants.

The log file paths are repeated across multiple test cases. Consider extracting these to constants at the top of the file to improve maintainability.

const LOG_FILE_PATHS = {
  DEFAULT: getFilePath('apps/watcher-type-default/logs/watcher-type-default/egg-agent.log'),
  CUSTOM: getFilePath('apps/watcher-custom-event-source/logs/watcher-custom-event-source/egg-agent.log'),
  FUZZY: getFilePath('apps/watcher-custom-event-source-fuzzy/logs/watcher-custom-event-source-fuzzy/egg-agent.log'),
};

Also applies to: 35-36, 67-68

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 097f79d and 1f0d980.

📒 Files selected for processing (3)
  • src/lib/boot.ts (1 hunks)
  • src/lib/types.ts (2 hunks)
  • test/watcher.test.ts (4 hunks)
🔇 Additional comments (4)
src/lib/types.ts (2)

22-24: LGTM! Type refinement improves clarity and accessibility.

The new EggWatcherApplicationCore interface properly extends EggApplicationCore and explicitly includes the watcher property, which aligns with the PR objective to export the watcher.


26-26: LGTM! Config type composition is clean.

The EggWatcherAppConfig type correctly combines EggAppConfig & WatcherConfig using intersection types.

src/lib/boot.ts (1)

6-6: LGTM! Type refinements improve type safety.

The constructor parameter and private member types are correctly updated to use EggWatcherApplicationCore, aligning with the new type system.

Also applies to: 9-9

test/watcher.test.ts (1)

30-30: LGTM! Type annotations improve type safety.

The watch callbacks now properly use the ChangeInfo type, with appropriate type intersections where additional properties are expected.

Also applies to: 44-44, 61-61

@fengmk2 fengmk2 merged commit 59a1880 into master Dec 20, 2024
21 checks passed
@fengmk2 fengmk2 deleted the fix-types branch December 20, 2024 02:26
fengmk2 pushed a commit that referenced this pull request Dec 20, 2024
[skip ci]

## [4.0.2](v4.0.1...v4.0.2) (2024-12-20)

### Bug Fixes

* should export watcher from EggWatcherApplicationCore ([#16](#16)) ([59a1880](59a1880))
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