Application State Store Creation and User API via ENTITY.setData({})

[EricEisaman]

• How do we flag or express data that should be stored in application state store?
  • ENTITY.setData{ position: object3D.position, newField: someValue } We want the setData method to detect pre-existing fields such as object3D.position and create handler's that tie into such field mutations and call the appropriate store actions. We will also monkeyPatch the existing entity with any new fields.
• What is the store hierarchy?
  • Initially create an EntityStore under the ApplicationStore. In the future add the ability to dynamically create categorical stores.
• How do these drive the dynamic creation of MST actions?
• Think about network updates mutating store state and how this should drive the store design.

NEXT TEST: Make sure EntityStore is created and we get logged RootStateStore snapshot.

[EricEisaman]

Perhaps use a Zod integration for types.

https://github.com/colinhacks/zod