<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Memoization on Coding Fox</title>
    <link>https://codingfox.dev/tags/memoization/</link>
    <description>Recent content in Memoization on Coding Fox</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 31 Jul 2026 00:00:00 +0200</lastBuildDate>
    <atom:link href="https://codingfox.dev/tags/memoization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Callback That Re-rendered an Entire Table</title>
      <link>https://codingfox.dev/post/react/react-memo-unstable-callback/</link>
      <pubDate>Fri, 31 Jul 2026 00:00:00 +0200</pubDate>
      <guid>https://codingfox.dev/post/react/react-memo-unstable-callback/</guid>
      <description>&lt;p&gt;&lt;em&gt;A short debugging story about &lt;code&gt;React.memo&lt;/code&gt;, prop drilling, and a missing &lt;code&gt;useCallback&lt;/code&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-symptom&#34;&gt;The symptom&lt;/h2&gt;&#xA;&lt;p&gt;We had an editable table: one row per item, each row with a couple of text inputs. Every row component was wrapped in &lt;code&gt;React.memo&lt;/code&gt;, specifically so that typing in one row wouldn&amp;rsquo;t force every other row to re-render. On a table with dozens of rows, that matters — otherwise every keystroke re-renders the whole table.&lt;/p&gt;&#xA;&lt;p&gt;It didn&amp;rsquo;t work. Typing a single character in one row&amp;rsquo;s input made &lt;em&gt;every&lt;/em&gt; row re-render, every time.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
