Provide a fallible map_entity api #17193
Labels
A-ECS
Entities, components, systems, and events
A-Networking
Sending data between clients, servers and machines
C-Feature
A new feature, making something new possible
D-Straightforward
Simple bug fixes and API improvements, docs, test and examples
S-Ready-For-Implementation
This issue is ready for an implementation PR. Go for it!
X-Contentious
There are nontrivial implications that should be thought through
What problem does this solve or what need does it fill?
The current MapEntity trait only provides a
map_entity(entity) -> Entity
method.There are cases where mapping the entity would fail, for example in networking. I think it would be helpful for the API to account for the possibility that the mapping fails.
Maybe we could provide a second method:
try_map_entity(entity) -> Result<Entity>
or just modify the main api to
map_entity(Entity) -> Result<Entity>
.I think historically the api was not fallible because the only EntityMapper was SceneEntityMapper which is not fallible.
(it either maps the entity or spawns a new one)
What solution would you like?
Update
map_entity
to returnResult<Entity>
What alternative(s) have you considered?
Unknown
The text was updated successfully, but these errors were encountered: