You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Its possible that all component gets a id, for example with a annotation or by method. if the blueprint-deserializer read this id inital, it gets all components and search the correct id. So It doesnt matter, what the name or the package of the component.
Do be faster at the second time, the blueprint-deserializer modify the blueprint and the it to the last correct "location/name" of the component. Next time the desializer is searching at this "location", if not found, it tries to handle the component with his Id (like described above)
okay so we need to override the defaut deserialisation by FasterXML for blueprints, to make this id mapping, right? because in the basic constructor, FasterXML will need to know which implementation of the EntityComponent to use.
When we move or rename a component in the code by refactoring, The serialized blueprints are to be rewritten manually.
Is there a simple way to avoid that?
The text was updated successfully, but these errors were encountered: