Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consistency between code and serialized data #4

Open
methusalah opened this issue Feb 6, 2016 · 2 comments
Open

Consistency between code and serialized data #4

methusalah opened this issue Feb 6, 2016 · 2 comments

Comments

@methusalah
Copy link

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?

@meltzow
Copy link

meltzow commented Feb 25, 2016

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)

@methusalah
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants