forked from rudderlabs/rudder-transformer
-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: [team]oncehub-83405: updating transformer version to "1.69.1" #78
Merged
so-abahadur
merged 322 commits into
team/technocrats
from
technocrats/ONCEHUB-83405-team1
Jun 27, 2024
Merged
feat: [team]oncehub-83405: updating transformer version to "1.69.1" #78
so-abahadur
merged 322 commits into
team/technocrats
from
technocrats/ONCEHUB-83405-team1
Jun 27, 2024
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
* fix: tiktok_ads: validate message.event type * fix: test cases * fix: validation for event name
* chore: add mixpanel batch size metrics * refactor: reduce duplicate code * fix: calculate batch metrics after chuncking
* feat: update movable ink batch size * test: add testcase for batching on max request size
* feat: onboard new destination bloomreach * refactor: move code to typescript * feat: add proxy and partial handling support * feat: onboard on router * chore: add proxy testcases * docs: add ref
* feat: support consent fields in GA4 * chore: code review changes * chore: code review changes * fix(ga4): processor tests --------- Co-authored-by: krishnachaitanya <[email protected]>
* feat: onboarding linkedin conversion api * fix: fixing network handler proxy v1 * fix: adding test cases round 1 * fix: network handler fix * fix: adding test cases processor router * fix: small edit * fix: adding auth network test cases * fix: adding auth network test cases part 2 * fix: editing logic + test cases * fix: adding util test cases * fix: corrrection in conversion logic and validation * fix: fix lint error * Apply suggestions from code review Co-authored-by: Gauravudia <[email protected]> * feat: review comments addressed * feat: review comments addressed * fix: review comments addressed * fix: aborting the revoked token PRs * fix: editing error category * fix: dest response example --------- Co-authored-by: Gauravudia <[email protected]>
fix: deployment file paths (rudderlabs#3216) Signed-off-by: Sai Sankeerth <[email protected]> Co-authored-by: Sai Sankeerth <[email protected]>
…ormer into release/v1.61.0
…abs#3238) chore: no success should return empty array
* feat: add tags to a company * feat: modified group call to attach user and add tags to company * feat: added some tests * feat: added error handler * fix: addressing comments * chore: refactoring tests * fix: some minor changes in tests
…labs#3025) * feat: add support in fb pixel for advertiser_tracking_enabled * chore: add corresponding router test * chore: update router tests descriptions in fb pixel
…tions (rudderlabs#3490) * fix: adding actual error messgae for default code in facebook destinations * fix: edit of test case description
…labs#3485) * fix: add missing userid and anonymousid for revenuecat source * chore: add test and related mock, address comment
* feat: onboard closeCRM source * fix: fixed timestamp issue * fix: fixed minor issues * fix: fixed payload * fix: test case
* feat: onboard user API for onesignal * chore: add aliases from one signal intg object * chore: add test cases * chore: add test cases+1 * chore: add test cases+2 * chore: small fixes * fix: lint errors * fix: lint errors+1 * fix: lint errors+2 * chore: rename file * chore: address comments
* fix: metadata tags capturing in v0 transformation
* chore: remove versionId, unused or unimportant stats
* chore: resolve bugsnag issue in braze * chore: resolve bugsnag issue in braze * chore: added tests * chore: added tests * fix: instead of throwing error now ignoring the undefined value in the products array
…ormer into technocrats/ONCEHUB-83405-team
ChandermohanOH
changed the title
[TEAM][ONCEHUB-83405]: Updating transformer version to "1.69.1"
feat: [team]oncehub-83405: updating transformer version to "1.69.1"
Jun 27, 2024
so-abahadur
approved these changes
Jun 27, 2024
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?
feat: [team]oncehub-83405: updating transformer version to "1.69.1"
Write a brief explainer on your code changes.
feat: [team]oncehub-83405: updating transformer version to "1.69.1"
What is the related Linear task?
Resolves INT-XXX
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.