From 9149d68d7082ecc4ce17b89c1153e08b415fcccc Mon Sep 17 00:00:00 2001 From: Srijan Date: Sun, 8 Mar 2026 22:49:50 +0530 Subject: [PATCH 1/2] Fix broken internal link in Component reference (anchor) --- src/content/reference/react/Component.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/reference/react/Component.md b/src/content/reference/react/Component.md index 2509aa7598a..4a62212da08 100644 --- a/src/content/reference/react/Component.md +++ b/src/content/reference/react/Component.md @@ -1009,7 +1009,7 @@ Deriving state leads to verbose code and makes your components difficult to thin #### Caveats {/*static-getderivedstatefromprops-caveats*/} -- This method is fired on *every* render, regardless of the cause. This is different from [`UNSAFE_componentWillReceiveProps`](#unsafe_cmoponentwillreceiveprops), which only fires when the parent causes a re-render and not as a result of a local `setState`. +- This method is fired on *every* render, regardless of the cause. This is different from [`UNSAFE_componentWillReceiveProps`](#unsafe_componentwillreceiveprops), which only fires when the parent causes a re-render and not as a result of a local `setState`. - This method doesn't have access to the component instance. If you'd like, you can reuse some code between `static getDerivedStateFromProps` and the other class methods by extracting pure functions of the component props and state outside the class definition. From fe16c34536138ce7e1fe870456cabfd0533ac23e Mon Sep 17 00:00:00 2001 From: Srijan Date: Sun, 8 Mar 2026 22:57:05 +0530 Subject: [PATCH 2/2] chore: trigger CLA check