Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -558,8 +558,14 @@ const ConversationAccordionItem = ({
{conversation.participant_name || conversation.title}
</Text>

{conversation.title && conversation.participant_name && (
<Tooltip label={conversation.title}>
{conversation.title && (
<Tooltip
label={
conversation.participant_name
? conversation.title
: t`Title auto-generated`
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Run pnpm messages:extract to capture the new Lingui string.

t\Title auto-generated`is a net-new translation key that won't land in the.po` files until extraction is run.

As per coding guidelines: "Use Trans component or t template literal for translations in frontend code, then run pnpm messages:extract to extract strings to .po files."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@echo/frontend/src/components/conversation/ConversationAccordion.tsx` at line
566, The new translation string t`Title auto-generated` in
ConversationAccordion.tsx is not yet extracted; run the extraction and commit
the updated .po files: execute `pnpm messages:extract` (from the repo root) to
update the locale catalogs, verify the new key from the t template literal in
the generated messages, and include the changed .po/.json files in your commit
alongside the ConversationAccordion.tsx change so translations are available at
runtime.

}
>
<IconInfoCircle size={14} className="text-gray-400" />
</Tooltip>
)}
Expand Down
Loading