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: updated isLoaded and isReady conditions for mixpanel #1650

Merged
merged 7 commits into from
Apr 2, 2024

Conversation

sandeepdsvs
Copy link
Contributor

@sandeepdsvs sandeepdsvs commented Mar 19, 2024

PR Description

Resolves INT-1852
Updated isLoaded and isReady conditions for mixpanel

Linear task (optional)

Linear task link

Cross Browser Tests

Please confirm you have tested for the following browsers:

  • Chrome
  • Firefox
  • IE11

Sanity Suite

  • All sanity suite test cases pass locally

Security

  • The code changed/added as part of this pull request won't create any security issues with how the software is being used.

Summary by CodeRabbit

  • Bug Fixes
    • Improved the accuracy of the isLoaded and isReady checks in the Mixpanel integration by updating the property used for verification.
  • Tests
    • Updated tests for isLoaded and isReady functionality in the Mixpanel integration to include asynchronous behavior.

Copy link
Contributor

coderabbitai bot commented Mar 19, 2024

Walkthrough

This update introduces a modification to the Mixpanel integration within the analytics-js-integrations package. Specifically, it adjusts how the isLoaded and isReady methods determine the loaded state of Mixpanel. Previously relying on the presence of a config property in the window.mixpanel object, the methods now look for a new __loaded property to make this determination.

Changes

File Path Change Summary
.../Mixpanel/browser.js Updated Mixpanel class with isNativeSDKLoaded property and related method changes.
.../Mixpanel/browser.test.js Changed window.mixpanel assignment, added loaded property in tests, and introduced new tests.

🐇✨
In the realm of code, where bugs often hide,
A change was made, with a small stride.
__loaded now leads, where config once did,
Ensuring Mixpanel's state is no longer hid.
So hop with joy, through fields of green,
For smoother analytics, now to be seen.
🌟🐰

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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/coderabbit-overrides.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.

__tests__/prodsdk.js Outdated Show resolved Hide resolved
Copy link
Contributor

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

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 14797b5 and 15cae49.
Files selected for processing (1)
  • packages/analytics-js-integrations/src/integrations/Mixpanel/browser.js (2 hunks)
Additional comments: 2
packages/analytics-js-integrations/src/integrations/Mixpanel/browser.js (2)
  • 101-101: The change to use __loaded instead of config in the isLoaded method aligns with the PR's objectives and improves the accuracy of the Mixpanel integration's loading state assessment.
  • 105-105: The update to the isReady method to check for the __loaded property instead of config is consistent with the PR's objectives and enhances the reliability of the Mixpanel integration's readiness assessment.

Copy link

codecov bot commented Mar 19, 2024

Codecov Report

Attention: Patch coverage is 83.33333% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 53.93%. Comparing base (da77fff) to head (9ef7158).

Files Patch % Lines
...-integrations/src/integrations/Mixpanel/browser.js 83.33% 1 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1650      +/-   ##
===========================================
+ Coverage    53.91%   53.93%   +0.02%     
===========================================
  Files          461      461              
  Lines        15613    15616       +3     
  Branches      3102     3098       -4     
===========================================
+ Hits          8417     8422       +5     
- Misses        5869     5899      +30     
+ Partials      1327     1295      -32     

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

Copy link

github-actions bot commented Mar 19, 2024

size-limit report 📦

Name Size (Base) Size (Current) Size Limit Status
Common Code - No bundling 15.81 KB 15.81 KB (0%) 16.5 KB
Remote Module Federation Mapping - CDN 330 B 330 B (0%) 512 B
Remote Module Federated Plugins - CDN 5.71 KB 5.71 KB (0%) 6 KB
Core ESM - NPM 7.64 KB 7.64 KB (0%) 8 KB
Core CJS - NPM 22.45 KB 22.45 KB (0%) 23 KB
Core - NPM 22.55 KB 22.55 KB (0%) 23 KB
Core Legacy - CDN 42.99 KB 42.99 KB (0%) 44 KB
Core - CDN 22.71 KB 22.71 KB (0%) 23 KB
Core (legacy build) - CDN - v1.1 31.55 KB 31.55 KB (0%) 32 KB
Core - NPM - v1.1 31.53 KB 31.53 KB (0%) 32 KB
Service Worker Module 22.64 KB 22.64 KB (0%) 24 KB
All Integrations (legacy build) - CDN 98.47 KB 98.45 KB (-0.02% ▼) 105 KB

Copy link
Contributor

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

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 15cae49 and 26e4b7f.
Files selected for processing (1)
  • packages/analytics-js-integrations/src/integrations/Mixpanel/browser.js (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • packages/analytics-js-integrations/src/integrations/Mixpanel/browser.js

Copy link
Contributor

@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: 1

Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 26e4b7f and 7385891.
Files selected for processing (2)
  • packages/analytics-js-integrations/tests/integrations/Mixpanel/browser.test.js (5 hunks)
  • packages/analytics-js-integrations/src/integrations/Mixpanel/browser.js (3 hunks)
Additional comments not posted (6)
packages/analytics-js-integrations/__tests__/integrations/Mixpanel/browser.test.js (2)

30-30: Adding a loaded property with expect.any(Function) in the expectations of the Mixpanel initialization tests is a good practice. It ensures that the loaded callback function is passed correctly during the initialization process. This change aligns with the modifications in the Mixpanel class to support the isLoaded and isReady enhancements.

Also applies to: 44-44, 59-59, 73-73


78-115: The introduction of new tests for isLoaded and isReady functionality with asynchronous behavior is commendable. These tests simulate the asynchronous loading of the Mixpanel SDK and verify that isLoaded and isReady correctly reflect the SDK's load state. This approach effectively tests the new functionality and ensures that it behaves as expected in asynchronous scenarios.

packages/analytics-js-integrations/src/integrations/Mixpanel/browser.js (4)

69-69: Adding isNativeSDKLoaded initialized to false is a straightforward and effective way to track the load state of the Mixpanel SDK. This property serves as the basis for the isLoaded and isReady methods to accurately reflect the SDK's load status.


97-99: The implementation of the loaded callback within the init method to set isNativeSDKLoaded to true is correct and aligns with the objective of accurately tracking the SDK's load state. This approach ensures that isLoaded and isReady can reliably indicate when the SDK is ready for use.


105-105: The isLoaded method's implementation, which simply returns the value of isNativeSDKLoaded, is appropriate and efficient. It directly reflects the load state of the Mixpanel SDK, fulfilling the requirement for the isLoaded functionality.


109-109: The isReady method's implementation, which delegates to isLoaded, is a sensible approach. It ensures consistency between isLoaded and isReady in terms of indicating the SDK's readiness, aligning with the intended enhancements.

Copy link
Contributor

@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

Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 7385891 and bc6be4f.
Files selected for processing (2)
  • packages/analytics-js-integrations/tests/integrations/Mixpanel/browser.test.js (5 hunks)
  • packages/analytics-js-integrations/src/integrations/Mixpanel/browser.js (2 hunks)
Files skipped from review as they are similar to previous changes (2)
  • packages/analytics-js-integrations/tests/integrations/Mixpanel/browser.test.js
  • packages/analytics-js-integrations/src/integrations/Mixpanel/browser.js

Copy link

sonarcloud bot commented Apr 2, 2024

@sandeepdsvs sandeepdsvs merged commit 80c76a1 into develop Apr 2, 2024
9 checks passed
@sandeepdsvs sandeepdsvs deleted the mixpanel_load_condition branch April 2, 2024 12:45
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.

None yet

4 participants