fix: update order_id in checkout events, messageId in pixel events #3794
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #3794 +/- ##
===========================================
- Coverage 89.06% 88.98% -0.08%
===========================================
Files 608 607 -1
Lines 32987 32808 -179
Branches 7807 7755 -52
===========================================
- Hits 29379 29195 -184
+ Misses 3331 3300 -31
- Partials 277 313 +36 ☔ View full report in Codecov by Sentry. |
krishna2020
reviewed
Oct 17, 2024
krishna2020
reviewed
Oct 18, 2024
|
Test report for this run is available at: https://test-integrations-dev.s3.amazonaws.com/integrations-test-reports/rudder-transformer/3794/test-report.html |
|
utsabc
approved these changes
Oct 21, 2024
krishna2020
approved these changes
Oct 21, 2024
sanpj2292
pushed a commit
that referenced
this pull request
Nov 5, 2024
…3794) * fix: update order_id in checkout events, messageId in pixel events * chore: add shopifyDetails support * chore: add shopifyDetails for shopify server side events from pixel * chore: set id property in the webhook event as messageId for pixel serverside event * chore: update tests
sanpj2292
pushed a commit
that referenced
this pull request
Nov 5, 2024
…3794) * fix: update order_id in checkout events, messageId in pixel events * chore: add shopifyDetails support * chore: add shopifyDetails for shopify server side events from pixel * chore: set id property in the webhook event as messageId for pixel serverside event * chore: update tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are the changes introduced in this PR?
order_idin checkout events.messageIdin pixel events.shopifyDetailsobjects support for pixel events inside context. (shopifyDetailsis a dump object with the complete event payload sent from Shopify.)What is the related Linear task?
Resolves INT-2789
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 in new readability format?
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.