List Custom Objects: Typo in Query String Parameter Name #2
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
The expected parameter is "properties"
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.
Description
When listing additional properties on custom objects, the expected query string parameter name is "properties" not "property"
I've tested this change locally and the properties I was requesting showed up after the change. The documentation from HubSpot is here: https://developers.hubspot.com/docs/api/crm/crm-custom-objects
Purpose
Checklist
I didn't see an obvious place to add tests, but I did test it locally and confirmed that the behavior changed to include the requested properties after the query string parameter name was changed.