Open
Description
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 return Result<Entity>
What alternative(s) have you considered?
Unknown
Metadata
Metadata
Assignees
Labels
Entities, components, systems, and eventsSending data between clients, servers and machinesA new feature, making something new possibleSimple bug fixes and API improvements, docs, test and examplesThis issue is ready for an implementation PR. Go for it!There are nontrivial implications that should be thought through