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: one_signal: Encode external_id in endpoint #3140

Merged
merged 2 commits into from Feb 28, 2024

Conversation

anantjain45823
Copy link
Contributor

@anantjain45823 anantjain45823 commented Feb 27, 2024

What are the changes introduced in this PR?

We are not encoding the external_id (like @ / + symbols) in endpoint ( for rack and group calls ) resulting in the root cause of a bug where one_signal throws an error “No users with external_id found”

What is the related Linear task?

Resolves INT-1696

Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here

Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?

N/A

Any new dependencies introduced with this change?

N/A

Any new generic utility introduced or modified. Please explain the changes.

N/A

Any technical or performance related pointers to consider with the change?

N/A

@coderabbitai review


Developer checklist

  • My code follows the style guidelines of this project

  • No breaking changes are being introduced.

  • All related docs linked with the PR?

  • All changes manually tested?

  • Any documentation changes needed with this change?

  • Is the PR limited to 10 file changes?

  • Is the PR limited to one linear task?

  • Are relevant unit and component test-cases added?

Reviewer checklist

  • Is the type of change in the PR title appropriate as per the changes?

  • Verified that there are no credentials or confidential data exposed with the changes.

Summary by CodeRabbit

  • Bug Fixes
    • Improved URL encoding for externalUserId in OneSignal API requests to ensure compatibility.
    • Updated test URLs to include encoded characters, enhancing test reliability for email addresses.

Copy link
Contributor

coderabbitai bot commented Feb 27, 2024

Important

Auto Review Skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository.

To trigger a single review, invoke the @coderabbitai review command.

Walkthrough

The recent updates focus on ensuring proper URL formatting for API requests within the OneSignal integration. Specifically, the changes involve encoding special characters in user identifiers, such as email addresses, within URLs. This includes using encodeURIComponent for the externalUserId in API endpoint constructions and encoding the @ symbol as %40 within URLs in the test data. These adjustments enhance compatibility and reliability in communication with the OneSignal API.

Changes

File Path Change Summary
src/v0/.../one_signal/transform.js Updated the endpoint URL construction by encoding the externalUserId using encodeURIComponent.
test/.../one_signal/processor/data.ts
test/.../one_signal/router/data.ts
Updated URLs to include encoded characters for email addresses, specifically replacing @ with %40.

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-tests for this file.
  • 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 tests 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 from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @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.
  • The JSON schema for the configuration file is available here.
  • 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

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@anantjain45823
Copy link
Contributor Author

@coderabbitai review

@devops-github-rudderstack
Copy link
Contributor

Copy link

codecov bot commented Feb 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.85%. Comparing base (9afcd7b) to head (11ed4e7).
Report is 11 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #3140      +/-   ##
===========================================
+ Coverage    84.59%   84.85%   +0.25%     
===========================================
  Files          493      494       +1     
  Lines        27308    27274      -34     
  Branches      6576     6554      -22     
===========================================
+ Hits         23101    23143      +42     
+ Misses        3754     3707      -47     
+ Partials       453      424      -29     

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

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 4be2997 and 11ed4e7.
Files selected for processing (3)
  • src/v0/destinations/one_signal/transform.js (2 hunks)
  • test/integrations/destinations/one_signal/processor/data.ts (5 hunks)
  • test/integrations/destinations/one_signal/router/data.ts (1 hunks)
Additional comments: 3
src/v0/destinations/one_signal/transform.js (2)
  • 125-125: The change correctly implements URL encoding for externalUserId in the track response builder using encodeURIComponent. This ensures special characters in externalUserId are properly encoded, preventing errors in API requests to OneSignal.
  • 166-166: Similarly, the URL encoding for externalUserId in the group response builder is correctly implemented. This modification is crucial for maintaining the integrity of API requests, especially when externalUserId contains special characters.
test/integrations/destinations/one_signal/router/data.ts (1)
  • 202-202: The encoding of the '@' symbol as '%40' in the external_user_id within the endpoint URL in the test data is correctly implemented. This change is essential for ensuring the test accurately reflects the conditions under which the code fix operates, specifically testing the URL encoding of special characters in external_user_id.

Copy link

sonarcloud bot commented Feb 27, 2024

@anantjain45823
Copy link
Contributor Author

@saikumarrs We might need to check for breaking change for this

@saikumarrs
Copy link
Member

@saikumarrs We might need to check for breaking change for this

Why do you think this is a breaking change?

@anantjain45823 anantjain45823 merged commit 8a20886 into develop Feb 28, 2024
26 checks passed
@anantjain45823 anantjain45823 deleted the fix.one_signal_encode_external_id_in_endpoint branch February 28, 2024 05:19
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