Add serialize method to ReflectSerialize (bevy_reflect)
#21171
Merged
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.
Objective
This change allows direct use of
.serialize(value, serializer)instead of the more verbose.get_serializable(value).serialize(serializer).Currently,
ReflectDeserialize,ReflectDeserializeWithRegistry, andReflectSerializeWithRegistryall provide adeserialize/serializemethod directly. It is inconsistent and somewhat odd thatReflectSerializeonly providesget_serializable.While the returned
Serializableobject does expose aserializemethod, I believeReflectSerializeshould offer a directserializemethod for better ergonomics.The existing
get_serializablemethod can still be used to obtain theSerializablestruct for testing or other specialized use cases. However, for typical serialization tasks, the direct.serialize(...)approach is clearer and more concise.Solution
Add
serializefunction forReflectSerialize.Testing
cd crates/bevy_reflect; cargo testcd crates/bevy_ecs; cargo testcd crates/bevy_asset; cargo testcargo run --example serializationShowcase
Click to view showcase