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

Typed stores #40

Closed
3 tasks
hu55a1n1 opened this issue Jan 7, 2022 · 1 comment · Fixed by #44
Closed
3 tasks

Typed stores #40

hu55a1n1 opened this issue Jan 7, 2022 · 1 comment · Fixed by #44
Assignees
Labels
enhancement New feature or request

Comments

@hu55a1n1
Copy link
Member

hu55a1n1 commented Jan 7, 2022

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.
@hu55a1n1 hu55a1n1 self-assigned this Jan 7, 2022
@hu55a1n1 hu55a1n1 added the enhancement New feature or request label Jan 7, 2022
@hu55a1n1
Copy link
Member Author

A decent implementation of this concept for the IBC module will require informalsystems/hermes#1760 to be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Status: Closed
Development

Successfully merging a pull request may close this issue.

1 participant