docs(en): use case for option function in defineStore #1309
Conversation
✅ Deploy Preview for pinia-official ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
This example could be useful for a cookbook entry |
trchopan
force-pushed
the
usecase-for-function-style-in-define-store
branch
from
abb6d95
to
ba2b79e
Compare
|
Thank you for your response. I've changed it to be a cookbook entry. |
trchopan
changed the title
There was a problem hiding this comment.
By the way, this pr looks misleading to me - I was wandering around to find some solution for dynamic store registration (implying passing different store ids to the factory function) and got here.
This pr, as I can see, better explains how stores handle states rather than how to create them dynamically. I think the contents should be refactored to better match the pr point.
|
|
||
| We can have a creator function like this | ||
|
|
||
| ```js |
There was a problem hiding this comment.
In this example, there should be ts if you want to use type annotations. Nothing critical, but the formatting would be a little bit better
No description provided.