From: Raúl López Date: Mon, 15 Jan 2024 08:02:19 +0000 (-0600) Subject: docs: Fixed Option-Stores link (#2552) X-Git-Tag: @pinia/nuxt@0.5.2-beta.0~61 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f78a12015d656dabdd7ea7aa1e2bdcea13909d73;p=thirdparty%2Fvuejs%2Fpinia.git docs: Fixed Option-Stores link (#2552) Link under section "What syntax should I pick?" `#option-stores` changed to `#Option-Stores` --- diff --git a/packages/docs/core-concepts/index.md b/packages/docs/core-concepts/index.md index c8cc37c8..981a1cc5 100644 --- a/packages/docs/core-concepts/index.md +++ b/packages/docs/core-concepts/index.md @@ -70,7 +70,7 @@ In _Setup Stores_: Note you **must** return **all state properties** in setup stores for pinia to pick them up as state. In other words, you cannot have _private_ state properties in stores. Not returning all state properties can break SSR, devtools, and other plugins. -Setup stores bring a lot more flexibility than [Option Stores](#option-stores) as you can create watchers within a store and freely use any [composable](https://vuejs.org/guide/reusability/composables.html#composables). However, keep in mind that using composables will get more complex when using [SSR](../cookbook/composables.md). +Setup stores bring a lot more flexibility than [Option Stores](#Option-Stores) as you can create watchers within a store and freely use any [composable](https://vuejs.org/guide/reusability/composables.html#composables). However, keep in mind that using composables will get more complex when using [SSR](../cookbook/composables.md). Setup stores are also able to rely on globally _provided_ properties like the Router or the Route. Any property [provided at the App level](https://vuejs.org/api/application.html#app-provide) can be accessed from the store using `inject()`, just like in components: