This repository has been archived by the owner on Apr 12, 2022. It is now read-only.
fix(hubspot): don't modify the options object when getting destination options #3011
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.
Change description
This was causing validation to fail because of unexpected
null
s, meaning that hubspot destinations could not be created.Because these were in here to clear out invalid values, this should no longer be necessary since core's validation introduced in #2988 will prevent these from being set in the first place.
Also fixed up the
filterEmptyOptions
method to also clearnull
s andundefined
sChecklists
Development
Impact
Please explain any security, performance, migration, or other impacts if relevant:
Code review