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

Adapt Specification to Make the Schema System Optional #11

Open
zicklag opened this issue Sep 1, 2024 · 0 comments
Open

Adapt Specification to Make the Schema System Optional #11

zicklag opened this issue Sep 1, 2024 · 0 comments

Comments

@zicklag
Copy link
Collaborator

zicklag commented Sep 1, 2024

Schema IDs should represent a hash unique to the schema, but that doesn't need to be a Leaf Schema formatted schema, it could be anything custom. The hash makes sure that we don't have a collision of schema IDs for different standards.

There should be a standard Leaf schema format, but it doesn't need to be prescriptive. If you don't understand the schema ID you can ignore it like any other component you don't know how to use.

This also makes it easier to adopt the Leaf protocol, because the schema format is one of the trickier pieces of it.

It also lets you use more common formats such as JSON for components, instead of Borsh, even though Borsh deserializing will be required for the core types such as entities.

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