Repository navigation
fix: tolerate an empty fields array in FileInfo - #437
Closed
TianHengZhuang wants to merge 1 commit into
Closed
TianHengZhuang wants to merge 1 commit into
TianHengZhuang wants to merge 1 commit into
Conversation
Member
|
Thanks for the contribution! I'm closing this, because it duplicates #436 |
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
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.
The Enterprise API returns an empty array for a file with no custom fields:
"fields": []FileInfo.fieldsis aMap<String, Object>, so Jackson throws aMismatchedInputExceptionon that response. This deserializes an empty array as
null(the same as a missing value),using the existing
EmptyArrayToNullDeserializerthat the other map fields already use.Closes #435