From aed540e3d3e9e7cf96a68265e831a743ec0e2935 Mon Sep 17 00:00:00 2001 From: Rich Harris Date: Sat, 3 Aug 2019 12:53:45 -0400 Subject: [PATCH] Update text.md --- site/content/tutorial/15-context/01-context-api/text.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/tutorial/15-context/01-context-api/text.md b/site/content/tutorial/15-context/01-context-api/text.md index aa028399b4..e577b9847e 100644 --- a/site/content/tutorial/15-context/01-context-api/text.md +++ b/site/content/tutorial/15-context/01-context-api/text.md @@ -46,4 +46,4 @@ const key = {}; We can use anything as a key — we could do `setContext('mapbox', ...)` for example. The downside of using a string is that different component libraries might accidentally use the same one; using an object literal means the keys are guaranteed not to conflict in any circumstance (since an object only has referential equality to itself, i.e. `{} !== {}` whereas `"x" === "x"`), even when you have multiple different contexts operating across many component layers. - > Remember that context is not inherently reactive. If you need context values to be reactive then you can pass a store into context, which *will* be reactive. +> Remember that context is not inherently reactive. If you need context values to be reactive then you can pass a store into context, which *will* be reactive.