From de6f0af32c1beaf8503b1fe7dc0d172af467c52d Mon Sep 17 00:00:00 2001 From: Andrew Mok <9611545+andrewmmc@users.noreply.github.com> Date: Tue, 21 Mar 2023 03:31:38 +0800 Subject: [PATCH] fix: fix broken link in cloneElement.md (#5766) --- src/content/reference/react/cloneElement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/reference/react/cloneElement.md b/src/content/reference/react/cloneElement.md index bdd5d9aa..86711f4d 100644 --- a/src/content/reference/react/cloneElement.md +++ b/src/content/reference/react/cloneElement.md @@ -70,7 +70,7 @@ Usually, you'll return the element from your component or make it a child of ano * You should only **pass children as multiple arguments to `cloneElement` if they are all statically known,** like `cloneElement(element, null, child1, child2, child3)`. If your children are dynamic, pass the entire array as the third argument: `cloneElement(element, null, listItems)`. This ensures that React will [warn you about missing `key`s](/learn/rendering-lists#keeping-list-items-in-order-with-key) for any dynamic lists. For static lists this is not necessary because they never reorder. -* `cloneElement` makes it harder to trace the data flow, so **try the [alternatives](/#alternatives) instead.** +* `cloneElement` makes it harder to trace the data flow, so **try the [alternatives](#alternatives) instead.** ---