You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the current store implementation, users can write arbitrary data to any path. This can be problematic because we know that some paths are only meant to store a certain type of data. For example -> paths of the form "clients/{identifier}/clientState" will always store ClientState. Here are some properties that would be nice to have ->
Enforce this at the type level
Disallow creation of multiple stores that point to the same path
Provide a way for users to define the (de)serialization at the type level.
The text was updated successfully, but these errors were encountered:
With the current store implementation, users can write arbitrary data to any path. This can be problematic because we know that some paths are only meant to store a certain type of data. For example -> paths of the form
"clients/{identifier}/clientState"
will always storeClientState
. Here are some properties that would be nice to have ->The text was updated successfully, but these errors were encountered: