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

Add a default way of serializing components #404

Open
patowen opened this issue Jun 21, 2024 · 0 comments
Open

Add a default way of serializing components #404

patowen opened this issue Jun 21, 2024 · 0 comments

Comments

@patowen
Copy link
Collaborator

patowen commented Jun 21, 2024

Currently, if we want to add a new component to Hypermine, boilerplate code has to be added to many different places in the codebase to allow data about this component to be transferred between the server and the client, along with additional boilerplate code to allow saving and loading.

When we start supporting a greater number of components, we should consider how to streamline the process of creating new ones, as this would make it less difficult for people less familiar with the codebase to add features.

One open design problem is how to serialize these components for saving, since naively relying on defaults would likely prevent save files from being compatible between versions of Hypermine.

As of June 2024, we probably need more components in place before we have enough information on how to perform such an abstraction.

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

No branches or pull requests

1 participant