From 9adbd58e77975071001e2f3f38d470e035c2d38b Mon Sep 17 00:00:00 2001 From: Gunnar Oledal Date: Tue, 28 Nov 2023 15:07:10 +0100 Subject: [PATCH] docs: extra clarification on why private state isn't allowed (#2507) * Some extra clarification on why private state isn't allowed * Update packages/docs/core-concepts/index.md --------- Co-authored-by: Eduardo San Martin Morote --- packages/docs/core-concepts/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/docs/core-concepts/index.md b/packages/docs/core-concepts/index.md index 64396e8a..b74d93e5 100644 --- a/packages/docs/core-concepts/index.md +++ b/packages/docs/core-concepts/index.md @@ -68,7 +68,7 @@ In _Setup Stores_: - `computed()`s become `getters` - `function()`s become `actions` -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. +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). -- 2.47.2