From b5f94d3b8687907ae232d4684c4c4c1de38e73a4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ji=C5=99=C3=AD=20Kopeck=C3=BD?= Date: Tue, 22 Jul 2025 15:01:29 +0200 Subject: [PATCH] Remove unnecessary memoization from a code example --- docs/usage/deriving-data-selectors.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/usage/deriving-data-selectors.md b/docs/usage/deriving-data-selectors.md index dea04cfaa9..c0d4c95bd6 100644 --- a/docs/usage/deriving-data-selectors.md +++ b/docs/usage/deriving-data-selectors.md @@ -228,7 +228,7 @@ const brokenSelector = createSelector( Similarly, a memoized selector should _never_ use `state => state` as an input! That will force the selector to always recalculate. ::: -In typical Reselect usage, you write your top-level "input selectors" as plain functions, and use `createSelector` to create memoized selectors that look up nested values: +In typical Reselect usage, you write your top-level "input selectors" as plain functions, and use `createSelector` to create memoized selectors that calculate derived values: ```js const state = { @@ -238,11 +238,9 @@ const state = { b: 10 } -const selectA = state => state.a +const selectA1 = state => state.a.first const selectB = state => state.b -const selectA1 = createSelector([selectA], a => a.first) - const selectResult = createSelector([selectA1, selectB], (a1, b) => { console.log('Output selector running') return a1 + b