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

chore: remove duplicate config named eventWhiteList #1652

Merged
merged 6 commits into from
Apr 26, 2024

Conversation

ItsSudip
Copy link
Member

@ItsSudip ItsSudip commented Mar 20, 2024

PR Description

Resolves INT-672
We are removing the duplicate config named eventWhiteList which is the same as the default SDK config named allowlist.

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

  • Refactor
    • Removed event whitelisting logic from TVSquared integration, allowing all events to be processed without filtering.

Copy link
Contributor

coderabbitai bot commented Mar 20, 2024

Walkthrough

The update involves a significant change in the TVSquared integration within the analytics package. Specifically, the event whitelisting feature has been removed. This adjustment simplifies the event handling process by eliminating the need to filter events based on a predefined list, potentially broadening the scope of events tracked without the previous restrictions.

Changes

File Path Change Summary
.../integrations/TVSquared/browser.js Removed event whitelisting logic from the TVSquared class.

🐰✨
A change has been made, oh so bright,
No more lists to check, into the night.
Events flow freely, like water so clear,
Tracking all, far and near.
In the code, we hop and leap,
Simplifying, no need to peep.
🌟🐇💻


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/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
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 28c9864.
Files selected for processing (1)
  • packages/analytics-js-integrations/src/integrations/TVSquared/browser.js (2 hunks)
Additional comments: 1
packages/analytics-js-integrations/src/integrations/TVSquared/browser.js (1)
  • 60-65: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [58-76]

The track method has been updated to remove the event whitelisting logic. This change aligns with the PR's objective to eliminate redundancy by removing the eventWhiteList configuration. It's important to ensure that this change does not inadvertently affect the tracking of events that should be filtered or handled differently. Consider adding tests or documentation to clarify how events are now expected to be handled without the whitelist logic.

Copy link

codecov bot commented Mar 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.14%. Comparing base (607c381) to head (f795d83).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1652      +/-   ##
===========================================
+ Coverage    54.12%   54.14%   +0.01%     
===========================================
  Files          462      462              
  Lines        15654    15648       -6     
  Branches      3107     3104       -3     
===========================================
- Hits          8473     8472       -1     
- Misses        5860     5877      +17     
+ Partials      1321     1299      -22     

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

Copy link

github-actions bot commented Mar 20, 2024

size-limit report 📦

Name Size (Base) Size (Current) Size Limit Status
Common Code - No bundling 15.78 KB 15.78 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.69 KB 7.69 KB (0%) 8 KB
Core CJS - NPM 22.89 KB 22.89 KB (0%) 23 KB
Core - NPM 23.03 KB 23.03 KB (0%) 23.5 KB
Core Legacy - CDN 43.35 KB 43.35 KB (0%) 44 KB
Core - CDN 23.21 KB 23.21 KB (0%) 23.5 KB
Core (legacy build) - CDN - v1.1 31.57 KB 31.57 KB (0%) 32 KB
Core - NPM - v1.1 31.56 KB 31.56 KB (0%) 32 KB
Service Worker Module 22.64 KB 22.64 KB (0%) 24 KB
All Integrations (legacy build) - CDN 98.62 KB 98.69 KB (+0.07% ▲) 105 KB

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@MoumitaM MoumitaM merged commit e85208b into develop Apr 26, 2024
9 checks passed
@MoumitaM MoumitaM deleted the chore.tvsquare_remove_config branch April 26, 2024 04:41
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.

5 participants