[RohithPariki]

Fixes #3147

Description

In frontend/src/components/Chat/ChatWindow.tsx, opening an empty Chat displayed the warning:

Converter choices could not be restored. Select and apply converters again before sending.
both while the page initially loaded and after a target was available, even when no converters had been selected and no draft recovery failed.

Root Cause

recoveredDraftWarningConversationId starts as null. In an empty chat or prior to opening/loading an existing conversation, viewedConversationId (activeConversationId ?? conversationId) is also null. The condition:
sx {recoveredDraftWarningConversationId === viewedConversationId && (
evaluated null === null as true, causing the warning message bar to render unconditionally on fresh empty chat sessions.

Solution

• Updated the warning render condition in ChatWindow.tsx to require that recoveredDraftWarningConversationId is truthy before comparing against viewedConversationId:
  sx {Boolean(recoveredDraftWarningConversationId) && recoveredDraftWarningConversationId === viewedConversationId && (
• Ensures the warning is only displayed when an actual draft restoration failed converter restoration (when missingConverterSelections: true sets the destination conversation ID), while keeping empty chats and successful restorations warning-free.
• Added regression tests in ChatWindow.test.tsx verifying:
  • No converter restoration warning on fresh empty chat with no conversation.
  • No converter restoration warning while fresh chat is loading without an active target.

Tests and Documentation

• Added unit tests in frontend/src/components/Chat/ChatWindow.test.tsx.
• Ran Jest test suite:
  • npx jest src/components/Chat/ChatWindow.test.tsx -t "converter restoration warning" (Passed)
• Ran type-check and linting:
  • npm run type-check (0 errors)
  • npm run lint (0 errors)

[Justin Song (jsong468)]

Thank you for the contribution!