fix(source-hubspot): fix custom streams path #58138
Merged
+11
−6
Conversation
This file contains hidden or 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
… custom object streams
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
tolik0
approved these changes
Apr 18, 2025
darynaishchenko
changed the title
darynaishchenko
changed the title
lazebnyi
approved these changes
Apr 22, 2025
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
https://developers.hubspot.com/changelog/breaking-change-removed-support-for-referencing-custom-object-types-by-base-name?utm_medium=email&utm_content=331333648&utm_source=hs_email
As a result, the base name format will no longer be supported after April 29th, 2025.
How
Using the short-hand custom object type name, aka GET
Review guide
User Impact
Can this PR be safely reverted and rolled back?