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

Multistore POC #17629

Closed
Tracked by #17314
alexanderbez opened this issue Sep 5, 2023 · 3 comments · Fixed by #17577
Closed
Tracked by #17314

Multistore POC #17629

alexanderbez opened this issue Sep 5, 2023 · 3 comments · Fixed by #17577
Assignees
Labels

Comments

@alexanderbez
Copy link
Contributor

No description provided.

@github-actions github-actions bot added the needs-triage Issue that needs to be triaged label Sep 5, 2023
@alexanderbez alexanderbez linked a pull request Sep 5, 2023 that will close this issue
20 tasks
@alexanderbez alexanderbez added C:Store WG: Storage and removed needs-triage Issue that needs to be triaged labels Sep 5, 2023
@alexanderbez alexanderbez self-assigned this Sep 5, 2023
@tac0turtle
Copy link
Member

minor nit, can we call multistore, store. multistore has trauma associated with it 😉

@alexanderbez
Copy link
Contributor Author

So you want to call what we've been calling "root multi store" just "store"? Doesn't that feel to generic and not descriptive? Maybe we can come up with something else all together?

@tac0turtle
Copy link
Member

yea works, we have had discussion about potentially doing a single store but allowing modules to extend into new stores if needed.

(yea store is confusing here )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants