actualbudget/actual

[Maintenance] loot-core should not rely on i18next

Open

#7,633 建立於 2026年4月26日

在 GitHub 查看
 (2 留言) (1 反應) (0 負責人)JavaScript (7,129 star) (603 fork)batch import
good first issuehelp wantedmaintenance

描述

The loot-core package should not reply on i18next. All user-facing translations should live in desktop-client package.

The objective here is to perform some refactors to remove usage of i18next from loot-core and then also remove this dependency from package.json.

Doing this will make managing translations easier as they will be self-container to a single package instead of scattered all over.

貢獻者指南

技術棧
javascriptnodejs
領域
backend
議題類型
refactor
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
knowledge of loot core packagefamiliarity with i18next
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
Identify all files in the loot core package that import or use i18next. Refactor each usage to either remove the translation call if it's not user facing, or move the translation logic to the desktop client package. After all usages are removed, delete i18next from loot core's package.json dependencies. Ensure no functionality is broken by verifying that all user facing strings are still translated via desktop client.