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: adding map for marketo known values and javascript known values #3037

Merged
merged 7 commits into from
Jan 31, 2024

Conversation

shrouti1507
Copy link
Contributor

@shrouti1507 shrouti1507 commented Jan 29, 2024

What are the changes introduced in this PR?

While running sync for a customer and we have come accross invalid id error for a huge number of events.

While debugging we found out that the data delivery was happening seemlessly but we have issue in reporting the failure and warning events.

while returning errors or warnings, marketo sends back all the fields of the erroneous events, along with its values and reason for failure, but no job ids are sent back

This the reason, we match all the events we already sent ( field-value ) to marketo with the response we get back from marketo.

The response itself can be clumsy and not so readable at various times. Upon research, we have seen that, if the data type of a field inside Marketo ( that we are making sure to get by sending one axios get call ) does not match with the data type that users send, it sends back a warning. That is why, we are checking, if data types are matching or not.

Now javascript understands 5 types of variables types:

  • number
  • string
  • boolean
  • undefined
  • object

we had considered any other data types of data to be of type string.

For example : marketo has email as a datatype, which is not easy for us to track. But for any email, the typeOf function returns string.

But we missed the logic that even if we consider email as string, the initial data type from marketo field is still email.

That is why this PR contains a suitable mapping for marketo known and javascript known data types

What is the related Linear task?

Resolves INT-1446

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 ?

Reason:

For example : marketo has email as a datatype, which is not easy for us to track. But for any email, the typeOf function returns string.

But we missed the logic that even if we consider email as string, the initial data type from marketo field is still email.

Changes :

We added a map which we convert marketo specific data types to javascript specific data types.
Example :
email --> string
integer --> number

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


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.

Copy link
Contributor

coderabbitai bot commented Jan 29, 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.

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.

.vscode/launch.json Outdated Show resolved Hide resolved
@devops-github-rudderstack
Copy link
Contributor

1 similar comment
@devops-github-rudderstack
Copy link
Contributor

@devops-github-rudderstack
Copy link
Contributor

Copy link

codecov bot commented Jan 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (5ad55a2) 87.09% compared to head (f7bf0cf) 87.14%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #3037      +/-   ##
===========================================
+ Coverage    87.09%   87.14%   +0.04%     
===========================================
  Files          530      530              
  Lines        28803    28802       -1     
  Branches      6859     6858       -1     
===========================================
+ Hits         25087    25099      +12     
+ Misses        3371     3360      -11     
+ Partials       345      343       -2     

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

Copy link
Contributor Author

@shrouti1507 shrouti1507 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@coderabbitai review

@devops-github-rudderstack
Copy link
Contributor

utsabc
utsabc previously approved these changes Jan 30, 2024
@devops-github-rudderstack
Copy link
Contributor

utsabc
utsabc previously approved these changes Jan 30, 2024
@devops-github-rudderstack
Copy link
Contributor

chandumlg
chandumlg previously approved these changes Jan 30, 2024
@shrouti1507 shrouti1507 dismissed stale reviews from chandumlg and utsabc via f7bf0cf January 31, 2024 04:36
@devops-github-rudderstack
Copy link
Contributor

Copy link

@shrouti1507 shrouti1507 merged commit 64ab555 into develop Jan 31, 2024
14 checks passed
@shrouti1507 shrouti1507 deleted the fix.marketo-jobStatus branch January 31, 2024 04:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants