github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 15:14:02 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #7633] [Maintenance] loot-core should not rely on i18next #117516

New Issue
Closed
opened 2026-06-11 12:44:41 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-06-11 12:44:41 -05:00
Owner
Copy Link

Originally created by @MatissJanis on GitHub (Apr 26, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7633

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.

Originally created by @MatissJanis on GitHub (Apr 26, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7633 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.
GiteaMirror added the maintenancegood first issue labels 2026-06-11 12:44:41 -05:00
GiteaMirror commented 2026-06-11 12:44:44 -05:00
Author
Owner
Copy Link

@SupaSeeka commented on GitHub (Apr 27, 2026):

I'll work on this.

<!-- gh-comment-id:4329153711 --> @SupaSeeka commented on GitHub (Apr 27, 2026): I'll work on this.
GiteaMirror commented 2026-06-11 12:44:44 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Apr 28, 2026):

For reference: https://github.com/actualbudget/actual/pull/7646#issuecomment-4338774595

<!-- gh-comment-id:4338781184 --> @MatissJanis commented on GitHub (Apr 28, 2026): For reference: https://github.com/actualbudget/actual/pull/7646#issuecomment-4338774595
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label good first issue maintenance
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#117516
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?