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: make sure mocks as global variable for multiple versions of muk-prop #4

Merged
merged 1 commit into from
Dec 22, 2024

Conversation

fengmk2
Copy link
Member

@fengmk2 fengmk2 commented Dec 22, 2024

Summary by CodeRabbit

  • New Features

    • Introduced a global mechanism for managing mock items, improving accessibility across module systems.
    • Added a new function to retrieve and manage mock items globally.
  • Bug Fixes

    • Enhanced the mock restoration process for better efficiency and reliability.

Copy link

coderabbitai bot commented Dec 22, 2024

Walkthrough

The pull request introduces a significant refactoring of mock item management in the src/index.ts file. The primary change involves replacing a local mocks array with a global symbol-based storage mechanism. This modification aims to improve mock item accessibility across different module systems by utilizing globalThis and a new getMocks() function. The mock and restore functions have been updated to work with this new global state management approach, centralizing mock item storage and simplification of the restoration process.

Changes

File Change Summary
src/index.ts - Replaced local mocks array with global symbol MOCKS
- Introduced getMocks() function to manage global mock state
- Updated mock function to use global mock storage
- Modified restore function to use while loop for clearing mocks

Sequence Diagram

sequenceDiagram
    participant Client
    participant Index as src/index.ts
    participant GlobalState as globalThis

    Client->>Index: mock()
    Index->>GlobalState: Check/Initialize MOCKS symbol
    Index->>GlobalState: Push mock item
    
    Client->>Index: restore()
    Index->>GlobalState: Retrieve MOCKS
    Index->>GlobalState: Pop all mock items
    Index->>GlobalState: Clear mock state
Loading

Possibly related PRs

Poem

🐰 A Rabbit's Ode to Global Mocks 🐰

Symbols dance where arrays once played,
Global state, a mockery parade!
getMocks() whispers, "Come this way!"
Modules unite without delay,
Mock magic spreads its fluffy might! 🌈

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 22, 2024

Open in Stackblitz

npm i https://pkg.pr.new/node-modules/muk-prop.js/@cnpmjs/muk-prop@4

commit: 684bdd2

Copy link

codecov bot commented Dec 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (79bf8af) to head (684bdd2).
Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master        #4   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           81        89    +8     
  Branches        10        12    +2     
=========================================
+ Hits            81        89    +8     

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

@fengmk2 fengmk2 merged commit 62e120b into master Dec 22, 2024
23 checks passed
@fengmk2 fengmk2 deleted the global-muks branch December 22, 2024 03:51
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 (3)
src/index.ts (3)

12-17: Ensure array-type consistency in getMocks() usage.
Currently, getMocks() unconditionally sets and retrieves an array from globalThis. Consider validating the stored object type (e.g., if a user accidentally overwrote this Symbol with a non-array value). Type checks might strengthen the resilience of getMocks() against runtime pollution.


72-74: Pop-based restoration: consider concurrency or parallel usage scenarios.
Although Node.js is single-threaded, library consumers may queue multiple mock/restore cycles. Using pop() in a while loop is fine in synchronous flows, but concurrency or parallel test runners may need a lock or a note that this isn’t thread-safe.

Would you like a concurrency-safe version or a big flashing note in the docs that this function isn’t thread-safe?


75-77: Validate fallback logic for inherited properties.
If hasOwnProperty = false, we unconditionally delete the property on the object. This assumes the original property exists on the prototype chain. Consider verifying that the property still exists upstream to avoid unexpected state if it was absent altogether.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1e2b166 and 684bdd2.

📒 Files selected for processing (1)
  • src/index.ts (3 hunks)
🔇 Additional comments (2)
src/index.ts (2)

9-9: Leverage uniqueness of the Symbol name.
Defining a Symbol with Symbol.for("@cnpmjs/muk-prop mocks") ensures a well-known global Symbol name. This is a good practice for bridging multiple module systems. Just make sure the name is unique enough to avoid collisions.


26-26: Double-check for undefined descriptors.
Forcing with “!” (in Object.getOwnPropertyDescriptor(obj, key)!) might mask potential undefined results. If “key” doesn’t exist at any level, this returns undefined. Consider fallback handling to ensure robust error reporting.

Run the following script to detect calls to mock() used on potentially non-existent properties:

fengmk2 pushed a commit that referenced this pull request Dec 22, 2024
[skip ci]

## [1.1.1](v1.1.0...v1.1.1) (2024-12-22)

### Bug Fixes

* make sure mocks as global variable for multiple versions of muk-prop ([#4](#4)) ([62e120b](62e120b))
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