fix: reduce unnecessary re-renders of custom Composer and Send components #2683
+55
−15
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.
Custom
renderComposerre-renders on every state change in v3.2.2, whereas v2.6.5 only re-rendered when relevant props changed. Root cause:InputToolbarused entirepropsobject asuseMemodependency, defeating memoization sincepropsis a new reference each render.Changes
InputToolbar.tsx
composerFragmentuseMemo:[renderComposer, composerHeight, text, textInputProps]sendFragmentuseMemo:[renderSend, text, label, ...]InputToolbarPropsinterfaceGiftedChat/index.tsx
textInputPropsobject passed to InputToolbarBefore/After
Fixes #2682
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.