From 5efbfa8e2b73244d2a9b55bee16f92e97587b55d Mon Sep 17 00:00:00 2001 From: Davi Oliveira da Silva Date: Mon, 8 Dec 2025 16:51:17 -0300 Subject: [PATCH] docs: Updated docs to include usage of $bindable for bidirectional bindings and its possible riscs (#17121) * docs: clarify usage of $bindable for bidirectional bindings and its possivle riscs * Update documentation/docs/02-runes/06-$bindable.md --------- Co-authored-by: Rich Harris --- documentation/docs/02-runes/06-$bindable.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/docs/02-runes/06-$bindable.md b/documentation/docs/02-runes/06-$bindable.md index c12c2bf490..3675a56b16 100644 --- a/documentation/docs/02-runes/06-$bindable.md +++ b/documentation/docs/02-runes/06-$bindable.md @@ -4,7 +4,7 @@ title: $bindable Ordinarily, props go one way, from parent to child. This makes it easy to understand how data flows around your app. -In Svelte, component props can be _bound_, which means that data can also flow _up_ from child to parent. This isn't something you should do often, but it can simplify your code if used sparingly and carefully. +In Svelte, component props can be _bound_, which means that data can also flow _up_ from child to parent. This isn't something you should do often — overuse can make your data flow unpredictable and your components harder to maintain — but it can simplify your code if used sparingly and carefully. It also means that a state proxy can be _mutated_ in the child.