refactor: change deserialization to prioritize most recent #122
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
Reverse the deserialization priority, so the most recently registered deserializers have priority. Previously, priority was given to the earliest registered. This switch makes it easier to add custom deserializers after bootstrap, as the built in ones already cover all data types and would intercept any json value before it got to a late registration.
Testing
Updated unit tests
Checklist: