Add support for Article.content_tag_ids field
- resolves #557
#558
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.
N.B. a potential risk of adding a new field to the model seems to be that any existing code using the client that was doing a overwrite of an existing article (by calling Zendesk.updateArticle(article) (without having recently read the article in question from the API, or where the Article instance has been created by copying a known set of fields from another Article instance) would have been preserving any pre-existing content_tags_id value on the article.
But if we add the field to the model, then any code like this will now be updating the content_tags_id field to be empty
This edge-case change in behaviour seems worthwhile, but may be worth documenting in release notes.