Translation Lint Remediation Plan

[kushu30]

Hi everyone,

Following the merge of #7364 (translation lint enforcement), the stricter translation checks are now active and have surfaced 32 files with translation inconsistencies across the codebase.

Breakdown:

• 28 files passing t as a prop/parameter instead of using useTranslation() locally
• 1 file calling t() without useTranslation()
• 3 files with missing translation keys
• 4 files with multiple keyPrefix warnings

To keep changes reviewable and reduce merge conflicts, I propose handling this in structured batches:

Batch 1: Fix the single direct t() misuse
Batch 2: AgendaFolder + AgendaItems components
Batch 3: Tag and Organization-related components
Batch 4: Recurrence-related shared components
Batch 5: EventListCard modals and related logic
Batch 6: Add missing translation keys
Batch 7: Resolve multiple keyPrefix warnings carefully

@palisadoes, could you please confirm if I should I open one tracking issue covering all 32 files and proceed batch wise via focused PRs?

 

[palisadoes]

Yes. Go ahead. Create a parent issue and make the batch issues sub-issues of the parent

 

[kushu30]

Alright!

 

[kushu30]

Hey, the parent issue is now made!