From 8eb90a20e6bca98b36a5995ee48772b9f4774819 Mon Sep 17 00:00:00 2001 From: Lucas Stahl <30933416+Stahlwalker@users.noreply.github.com> Date: Tue, 14 Nov 2023 10:25:52 -0600 Subject: [PATCH] Fixed SEO Issue fixed http issue --- packages/docs/src/routes/api/qwik/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/docs/src/routes/api/qwik/index.md b/packages/docs/src/routes/api/qwik/index.md index d1233fe2a2b..0a34000b6e7 100644 --- a/packages/docs/src/routes/api/qwik/index.md +++ b/packages/docs/src/routes/api/qwik/index.md @@ -1924,7 +1924,7 @@ At times it is necessary to store values on a store that are non-serializable. N You can use `noSerialize()` to mark a value as non-serializable. The value is persisted in the Store but does not survive serialization. The implication is that when your application is resumed, the value of this object will be `undefined`. You will be responsible for recovering from this. -See: [noSerialize Tutorial](http://qwik.builder.io/tutorial/store/no-serialize) +See: [noSerialize Tutorial](https://qwik.builder.io/tutorial/store/no-serialize) ```typescript noSerialize: (input: T) => NoSerialize;