From fe3f21dad9dfaf60c500a26d911aaedd67923f7b Mon Sep 17 00:00:00 2001 From: Nicolas Cura <59953189+NCura@users.noreply.github.com> Date: Wed, 6 May 2026 09:54:22 +0200 Subject: [PATCH] Update references from create_effect to Effect::new --- src/reactivity/14_create_effect.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/reactivity/14_create_effect.md b/src/reactivity/14_create_effect.md index b2346e4..ea8d072 100644 --- a/src/reactivity/14_create_effect.md +++ b/src/reactivity/14_create_effect.md @@ -82,7 +82,7 @@ let b = move || a.get() * 2; If you need to synchronize some reactive value with the non-reactive world outside—like a web API, the console, the filesystem, or the DOM—writing to a signal in an effect is a fine way to do that. In many cases, though, you’ll find that you’re really writing to a signal inside an event listener or something else, not inside an effect. In these cases, you should check out [`leptos-use`](https://leptos-use.rs/) to see if it already provides a reactive wrapping primitive to do that! -> If you’re curious for more information about when you should and shouldn’t use `create_effect`, [check out this video](https://www.youtube.com/watch?v=aQOFJQ2JkvQ) for a more in-depth consideration! +> If you’re curious for more information about when you should and shouldn’t use `Effect::new`, [check out this video](https://www.youtube.com/watch?v=aQOFJQ2JkvQ) for a more in-depth consideration! ## Effects and Rendering @@ -208,7 +208,7 @@ fn CreateAnEffect() -> impl IntoView { view! {

- "create_effect" + "Effect::new" " Version"