Should I use memo? #4116
-
|
If I have a component that I'm pretty sure should only update when the props change, should I wrap it in I'm asking because it's located in |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
You can use it, sure. To paraphrase Marvin, it's in |
Beta Was this translation helpful? Give feedback.
-
|
How would one go about component level memoization with signals then? |
Beta Was this translation helpful? Give feedback.
-
|
Can you provide an example? Generally you shouldn't need that with signals, the API fundamentally avoids memoization issues. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I am actually asking you for an example how I can use signals to achieve memoization. Surely you didn't mean to store a component in a signal, right? |
Beta Was this translation helpful? Give feedback.
-
|
Signals themselves are "memoized" (I use this to refer more to the end result/DX than traditional React-flavor memoization) and only update that which subscribes to them. The concept of memoizing components is therefore redundant & unnecessary.
|
Beta Was this translation helpful? Give feedback.
You can use it, sure.
To paraphrase Marvin, it's in
preact/compatas we think it's not a great API, comparatively. Signals are a much more attractive approach for dealing with unnecessary rerenders, and goes a lot further thanmemodoes. We don't havememoin core because we don't think it's an essential piece, not because it doesn't serve a purpose.