✨ core: nested schema objects #138
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently if you use nested objects in a schema the object will simply be shared between all instances of that trait data. To make it unique an initializer is necessary.
However, I am not sure I like this being the default behavior. I am leaning towards making it so all schema objects are read the same no matter their nesting. IE all schema objects are transformed into SoA stores. In this case if you wanted to share an object you use an initializer to have your own store logic.
Follow up question: Should the same be true for arrays?