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.
Benefit from pickles referential serialization to reduce reflex event payload size
This is especially useful when dealing with complex sqlalchemy models which can contain circular and self-referencing relationships
Serialization should also be faster? (did not measure the impact yet)
We could drop most of the serializers and rely on pickle. You can test this with bare sqlalchemy models like this:
Advantages:
[{a:1}].includes({a:1})
isfalse
in jsDisadvantages: