feat(Entity): OOP-ify the array deserialization mess #566
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.
ArrayList deserialization from JSON has been very messy. There's a huge switch statement that goes through each possible property name to find the type. Not only is that unmaintainable but also leads to property conflicts:
For example an entity that has an
uploads
property of string and an entity that also has anuploads
property but of API.Attachment cannot co-exist. We've been lucky so far that there haven't been any conflicts.This PR creates a virtual function that returns a
Type
for a property name, allowing descendants to override it for their needs.