You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I added the field Articles.contentTagIds in this commit, I trusted the example responses in the Zendesk documentation & so added the field as a List<Long>
But it turns out that the articles API docs were wrong & the IDs are really String values (not Long)
Evidence:
The docs for the content_tags resource show it as a String.
And an example response from my Zendesk instance's Articles API has String values:
Describe the bug
When I added the field Articles.contentTagIds in this commit, I trusted the example responses in the Zendesk documentation & so added the field as a
List<Long>
But it turns out that the articles API docs were wrong & the IDs are really
String
values (notLong
)Evidence:
The docs for the content_tags resource show it as a String.
And an example response from my Zendesk instance's Articles API has String values:
I would expect this bug to cause deserialisation errors when parsing article responses that contain content_tag_ids value
I'll get a PR to fix in ASAP.
The text was updated successfully, but these errors were encountered: