Add partial Map support to assembler
#180
Open
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.
Allow Assembler customizations to replace Object instances with Map without affecting the rest of its functionality. It makes it much more efficient when deserializing large "objects" that are functionally lookup tables, with minimal customization.
The mechanism for determining when replacement with Map is used is out-of-scope. There are no new APIs added.
I have a use case where the parsed JSON consists primarily of large lookup tables (700+ entries per table):
{ "modules": { "mod000": { /*...*/ }, "mod001": { /*...*/ }, //... "mod750": { /*...*/ } }, "metadata": { /*...*/ } }The table is transformed to
Mapfor actual usage, which is a somewhat awkward process. WithAssemblermodified to understandMap, it becomes much simpler.Doing this with monkey patching is possible but very awkward due to the way
Assembler's internal methods are connected. Extending_saveValue()to coverMapmakes this basically trivial..