From 3411540707b9de1e2e2d6e9d96e14f291b23d986 Mon Sep 17 00:00:00 2001
From: Alwin Lohrie <46248939+niwla23@users.noreply.github.com>
Date: Tue, 19 Jul 2022 20:16:47 +0200
Subject: [PATCH 1/3] Add warning about non-serializable datatypes in useState

---
 docs/content/2.guide/2.features/6.state-management.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/content/2.guide/2.features/6.state-management.md b/docs/content/2.guide/2.features/6.state-management.md
index 727064711ce..f6ea5b09e2b 100644
--- a/docs/content/2.guide/2.features/6.state-management.md
+++ b/docs/content/2.guide/2.features/6.state-management.md
@@ -13,6 +13,9 @@ Nuxt provides `useState` composable to create a reactive and SSR-friendly shared
 
 ## Best practices
 
+::alert{type=warning}
+Note that data inside `useState` must be serializable. This means you can't use functions or classes in `useState`.
+::
 ::alert{type=danger icon=🚨}
 Never define `const state = ref()` outside of `<script setup>` or `setup()` function.<br>
 Such state will be shared across all users visiting your website and can lead to memory leaks!

From 33be782f51f4dfe9fd40970500971c06527d2db5 Mon Sep 17 00:00:00 2001
From: Alwin Lohrie <46248939+niwla23@users.noreply.github.com>
Date: Tue, 19 Jul 2022 20:43:00 +0200
Subject: [PATCH 2/3] Move out of best practices section

---
 docs/content/2.guide/2.features/6.state-management.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/content/2.guide/2.features/6.state-management.md b/docs/content/2.guide/2.features/6.state-management.md
index f6ea5b09e2b..347acb148b6 100644
--- a/docs/content/2.guide/2.features/6.state-management.md
+++ b/docs/content/2.guide/2.features/6.state-management.md
@@ -10,12 +10,13 @@ Nuxt provides `useState` composable to create a reactive and SSR-friendly shared
 ::alert{icon=👉}
 `useState` only works during `setup` or [`Lifecycle Hooks`](https://vuejs.org/api/composition-api-lifecycle.html#composition-api-lifecycle-hooks).
 ::
-
-## Best practices
-
 ::alert{type=warning}
 Note that data inside `useState` must be serializable. This means you can't use functions or classes in `useState`.
 ::
+
+## Best practices
+
+
 ::alert{type=danger icon=🚨}
 Never define `const state = ref()` outside of `<script setup>` or `setup()` function.<br>
 Such state will be shared across all users visiting your website and can lead to memory leaks!

From 323d09622d65fdf545485e25d10babfcb63580d3 Mon Sep 17 00:00:00 2001
From: Alwin Lohrie <46248939+niwla23@users.noreply.github.com>
Date: Wed, 20 Jul 2022 00:54:21 +0200
Subject: [PATCH 3/3] fix linter issues

---
 docs/content/2.guide/2.features/6.state-management.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/docs/content/2.guide/2.features/6.state-management.md b/docs/content/2.guide/2.features/6.state-management.md
index 347acb148b6..96e81ee150e 100644
--- a/docs/content/2.guide/2.features/6.state-management.md
+++ b/docs/content/2.guide/2.features/6.state-management.md
@@ -16,7 +16,6 @@ Note that data inside `useState` must be serializable. This means you can't use
 
 ## Best practices
 
-
 ::alert{type=danger icon=🚨}
 Never define `const state = ref()` outside of `<script setup>` or `setup()` function.<br>
 Such state will be shared across all users visiting your website and can lead to memory leaks!