fix(react): add missing unique key props to ChatInputFormattingToolba…

[deepak0x]

This PR fixes a common React warning:

Warning: Each child in a list should have a unique "key" prop

The warning occurred in the ChatInputFormattingToolbar component and was caused by several elements being rendered as part of dynamic lists without providing a unique key prop. This made it harder for React to correctly track and optimize updates to these elements.

---

Closes #1098

Changes

Updated packages/react/src/views/ChatInput/ChatInputFormattingToolbar.js:

• Added key="audio" to the AudioMessageRecorder component.
• Added key="video" to the VideoMessageRecorder component.
• Replaced empty fragments (<>) with <React.Fragment key={item.name}> for mapped formatting buttons (bold, italic, strike, etc.).

---

[sudorishabh]

Bro, I saw the same issue earlier and searched to see if there was already an open PR. I came across your implementation. Great work. However, there’s a small improvement that can be made. You don’t actually need <React.Fragment> here. React only cares about the key on the top-level element returned from the map. Since the key is already on the component, the fragment is unnecessary and can be removed entirely.

[Spiral-Memory]

LGTM