Skip to content

fix: data plane events buffer on load option flag #1997

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

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

saikumarrs
Copy link
Member

@saikumarrs saikumarrs commented Jan 9, 2025

PR Description

Please include a summary of the change along with the relevant motivation and context.

Linear task (optional)

https://linear.app/rudderstack/issue/SDK-2862/buffer-data-plane-events-until-ready

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

  • Refactor
    • Improved internal code organization for analytics and event repository management.
    • Streamlined methods for handling event queue and destination settings.
    • Encapsulated logic for managing data plane events and active destinations.

@saikumarrs saikumarrs self-assigned this Jan 9, 2025
Copy link
Contributor

coderabbitai bot commented Jan 9, 2025

📝 Walkthrough
## Walkthrough

The pull request introduces refactoring in two key analytics-related classes: `Analytics` and `EventRepository`. In the `Analytics` class, a new private method `setActiveDestinations` is added to encapsulate the logic for setting active destinations, replacing inline code. Similarly, in the `EventRepository` class, a new private method `startDpEventsQueue` is introduced to manage the data plane events queue initialization, consolidating and simplifying the event buffering and queue start conditions.

## Changes

| File | Change Summary |
|------|----------------|
| `packages/analytics-js/src/components/core/Analytics.ts` | Added private `setActiveDestinations()` method to centralize logic for setting active destinations |
| `packages/analytics-js/src/components/eventRepository/EventRepository.ts` | Added private `startDpEventsQueue()` method to manage data plane events queue initialization and buffering logic |

## Possibly related PRs

- #2100: Refactors internal logic of starting the data plane events queue in the `EventRepository` class, closely related to buffering and queue management improvements.
  
## Suggested reviewers

- koladilip

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

📜 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 04c5fa8 and 663d9cd.

📒 Files selected for processing (2)
  • packages/analytics-js/src/components/core/Analytics.ts (2 hunks)
  • packages/analytics-js/src/components/eventRepository/EventRepository.ts (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • packages/analytics-js/src/components/core/Analytics.ts
  • packages/analytics-js/src/components/eventRepository/EventRepository.ts
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Bundle size checks
  • GitHub Check: Unit Tests and Lint
  • GitHub Check: Security and code quality checks

🪧 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

codecov bot commented Jan 9, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.62%. Comparing base (2294bdd) to head (663d9cd).
Report is 43 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1997      +/-   ##
===========================================
+ Coverage    61.61%   61.62%   +0.01%     
===========================================
  Files          478      478              
  Lines        16450    16455       +5     
  Branches      3265     3267       +2     
===========================================
+ Hits         10136    10141       +5     
+ Misses        5084     5066      -18     
- Partials      1230     1248      +18     

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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

🧹 Nitpick comments (1)
packages/analytics-js/src/components/eventRepository/EventRepository.ts (1)

125-130: Consider a more descriptive variable name.

The variable shouldBufferDpEvents could be more descriptive to better reflect its specific purpose.

-    const shouldBufferDpEvents = bufferEventsUntilReady && hybridDestExist;
+    const shouldBufferForHybridDestinations = bufferEventsUntilReady && hybridDestExist;
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2b6b668 and 7a9d55e.

📒 Files selected for processing (2)
  • packages/analytics-js/src/components/core/Analytics.ts (2 hunks)
  • packages/analytics-js/src/components/eventRepository/EventRepository.ts (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Security and code quality checks
  • GitHub Check: Unit Tests and Lint
  • GitHub Check: Bundle size checks
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (5)
packages/analytics-js/src/components/eventRepository/EventRepository.ts (3)

119-121: LGTM! Appropriate condition for starting data plane events queue.

The condition correctly initiates the data plane events queue when pre-consent buffering is not required.


Line range hint 124-152: LGTM! Well-structured queue management implementation.

The method effectively consolidates the data plane events queue management logic with appropriate buffering conditions and safety timeout mechanism.


156-164: LGTM! Consistent use of centralized queue management.

The resume method correctly uses the new startDpEventsQueue method while maintaining existing queue clearing logic.

packages/analytics-js/src/components/core/Analytics.ts (2)

294-296: LGTM! Good extraction of active destinations setup.

The code organization is improved by moving the active destinations setup to a dedicated method.


304-312: LGTM! Well-encapsulated active destinations setup.

The new method effectively encapsulates the plugin invocation logic for setting active destinations, promoting code reuse and maintainability.

coderabbitai[bot]
coderabbitai bot previously approved these changes Jan 9, 2025
Copy link

github-actions bot commented Jan 9, 2025

size-limit report 📦

Name Size Delta Limit check
Common - No bundling 18.01 KB 0 B (0% 🟢) 19 KB (✅)
Cookies Utils - Legacy - NPM (ESM) 1.54 KB 0 B (0% 🟢) 2 KB (✅)
Cookies Utils - Legacy - NPM (CJS) 1.74 KB 0 B (0% 🟢) 2 KB (✅)
Cookies Utils - Legacy - NPM (UMD) 1.52 KB 0 B (0% 🟢) 2 KB (✅)
Cookies Utils - Modern - NPM (ESM) 1.16 KB 0 B (0% 🟢) 1.5 KB (✅)
Cookies Utils - Modern - NPM (CJS) 1.39 KB 0 B (0% 🟢) 1.5 KB (✅)
Cookies Utils - Modern - NPM (UMD) 1.15 KB 0 B (0% 🟢) 1.5 KB (✅)
Plugins Module Federation Mapping - Legacy - CDN 332 B 0 B (0% 🟢) 512 B (✅)
Plugins Module Federation Mapping - Modern - CDN 331 B 0 B (0% 🟢) 512 B (✅)
Plugins - Legacy - CDN 14.21 KB 0 B (0% 🟢) 14.5 KB (✅)
Plugins - Modern - CDN 5.64 KB 0 B (0% 🟢) 6 KB (✅)
Core (v1.1) - NPM (ESM) 29.86 KB 0 B (0% 🟢) 32 KB (✅)
Core (v1.1) - NPM (CJS) 30.05 KB 0 B (0% 🟢) 32 KB (✅)
Core (v1.1) - NPM (UMD) 29.91 KB 0 B (0% 🟢) 32 KB (✅)
Core (Content Script - v1.1) - NPM (ESM) 29.44 KB 0 B (0% 🟢) 30.5 KB (✅)
Core (Content Script - v1.1) - NPM (CJS) 29.62 KB 0 B (0% 🟢) 30.5 KB (✅)
Core (Content Script - v1.1) - NPM (UMD) 29.44 KB 0 B (0% 🟢) 30.5 KB (✅)
Core (v1.1) - Legacy - CDN 31.8 KB 0 B (0% 🟢) 32.5 KB (✅)
Core (v1.1) - Modern - CDN 29.77 KB 0 B (0% 🟢) 32 KB (✅)
All Integrations - Legacy - CDN 96.09 KB 0 B (0% 🟢) 96.5 KB (✅)
All Integrations - Modern - CDN 90.65 KB 0 B (0% 🟢) 91 KB (✅)
Service Worker - Legacy - NPM (ESM) 30.3 KB 0 B (0% 🟢) 31 KB (✅)
Service Worker - Legacy - NPM (CJS) 30.54 KB 0 B (0% 🟢) 31 KB (✅)
Service Worker - Legacy - NPM (UMD) 30.34 KB 0 B (0% 🟢) 31 KB (✅)
Service Worker - Modern - NPM (ESM) 25.47 KB 0 B (0% 🟢) 26 KB (✅)
Service Worker - Modern - NPM (CJS) 25.74 KB 0 B (0% 🟢) 26.5 KB (✅)
Service Worker - Modern - NPM (UMD) 25.52 KB 0 B (0% 🟢) 26 KB (✅)
Load Snippet 765 B 0 B (0% 🟢) 1 KB (✅)
Core - Legacy - NPM (ESM) 47.71 KB 0 B (0% 🟢) 48 KB (✅)
Core - Legacy - NPM (CJS) 47.99 KB 20 B (+0.05% 🔺) 48.2 KB (✅)
Core - Legacy - NPM (UMD) 47.77 KB 37 B (+0.08% 🔺) 48 KB (✅)
Core - Legacy - CDN 47.83 KB -2 B (-0.01% 🟢) 48 KB (✅)
Core - Modern - NPM (ESM) 26.74 KB 63 B (+0.24% 🔺) 27 KB (✅)
Core - Modern - NPM (CJS) 26.96 KB 16 B (+0.06% 🔺) 27.2 KB (✅)
Core - Modern - NPM (UMD) 26.77 KB 21 B (+0.08% 🔺) 27 KB (✅)
Core - Modern - CDN 26.99 KB 16 B (+0.06% 🔺) 27.5 KB (✅)
Core (Bundled) - Legacy - NPM (ESM) 47.71 KB 0 B (0% 🟢) 48 KB (✅)
Core (Bundled) - Legacy - NPM (CJS) 47.94 KB -60 B (-0.13% 🟢) 48.2 KB (✅)
Core (Bundled) - Legacy - NPM (UMD) 47.77 KB 37 B (+0.08% 🔺) 48 KB (✅)
Core (Bundled) - Modern - NPM (ESM) 38.9 KB 16 B (+0.05% 🔺) 39 KB (✅)
Core (Bundled) - Modern - NPM (CJS) 39.15 KB 15 B (+0.04% 🔺) 39.5 KB (✅)
Core (Bundled) - Modern - NPM (UMD) 38.92 KB -3 B (-0.01% 🟢) 39 KB (✅)
Core (Content Script) - Legacy - NPM (ESM) 47.7 KB 18 B (+0.04% 🔺) 48 KB (✅)
Core (Content Script) - Legacy - NPM (CJS) 47.97 KB 57 B (+0.12% 🔺) 48 KB (✅)
Core (Content Script) - Legacy - NPM (UMD) 47.78 KB 83 B (+0.17% 🔺) 48 KB (✅)
Core (Content Script) - Modern - NPM (ESM) 38.82 KB 10 B (+0.03% 🔺) 39 KB (✅)
Core (Content Script) - Modern - NPM (CJS) 39.1 KB 4 B (+0.01% 🔺) 39.2 KB (✅)
Core (Content Script) - Modern - NPM (UMD) 38.86 KB 15 B (+0.04% 🔺) 39 KB (✅)

Copy link

Hello! This PR has been open for 20 days without any activity. Therefore, it's considered as stale and is scheduled to be closed in 10 days. If you're still working on this, please remove the 'Stale' label or add a comment to keep it open. Thanks for your contribution!

Copy link

Hello! This PR has been open for 20 days without any activity. Therefore, it's considered as stale and is scheduled to be closed in 10 days. If you're still working on this, please remove the 'Stale' label or add a comment to keep it open. Thanks for your contribution!

Copy link

Hello! This PR has been open for 20 days without any activity. Therefore, it's considered as stale and is scheduled to be closed in 10 days. If you're still working on this, please remove the 'Stale' label or add a comment to keep it open. Thanks for your contribution!

@github-actions github-actions bot added Stale and removed Stale labels Mar 13, 2025
Copy link

github-actions bot commented Apr 3, 2025

Hello! This PR has been open for 20 days without any activity. Therefore, it's considered as stale and is scheduled to be closed in 10 days. If you're still working on this, please remove the 'Stale' label or add a comment to keep it open. Thanks for your contribution!

@github-actions github-actions bot added the Stale label Apr 3, 2025
@saikumarrs saikumarrs removed the Stale label Apr 3, 2025
Copy link

github-actions bot commented May 8, 2025

Hello! This PR has been open for 20 days without any activity. Therefore, it's considered as stale and is scheduled to be closed in 10 days. If you're still working on this, please remove the 'Stale' label or add a comment to keep it open. Thanks for your contribution!

@github-actions github-actions bot added the Stale label May 8, 2025
@saikumarrs saikumarrs removed the Stale label May 8, 2025
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