Optimize SendButton memo comparison for fewer re-renders #889
+2
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Optimization for SendButton re-rendering
What changed
Optimized the React.memo comparison function for SendButton to only trigger re-renders when the disabled state would actually change.
The comparison now explicitly checks for transitions between empty/non-empty states rather than re-rendering on every input change:
Why this matters
This change significantly reduces unnecessary re-renders when typing in the input field. Previously, any character added or removed would trigger a re-render of the SendButton component, even though its visual state only changes when transitioning between empty and non-empty states.
Performance impact
In large chat applications with frequent typing, this optimization helps reduce rendering overhead and improves responsiveness, particularly on lower-end devices.
Testing
Verified that the button properly updates its disabled state when: