Start removing JsonIn
by supporting a more verbose deserialize()
pattern.
#51449
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.
Summary
Infrastructure "Support deserialize directly from JsonObject/Array/Value/etc"
Purpose of change
JsonIn
is deprecated in #50143, which converts json loading from text to binary. Unfortunately, the entiredeserialize()
pattern requires acceptingJsonIn
as an argument. To make that change more feasible we should do as much ahead-of-time removal ofJsonIn
as possible.Describe the solution
Many of the existing uses of
JsonIn
in thedeserialize()
pattern just immediately convert to aJsonObject
orJsonArray
, dropping into the 'object oriented'deserialize
pattern off the streaming patten. We can extendJsonIn::read()
to support types with adeserialize
method taking eitherJsonIn
orJsonValue
-convertible types. Then we can push the actual used type into the signature and remove a large number of unnecessary references toJsonIn
.Describe alternatives you've considered
Supporting
JsonIn
on top ofFlexBuffers
was attempted and discarded as discussed on #50143.Testing
CI, loaded and created games.