Enable Indonesian (`id`) as an in-app locale (#715)

* Initial plan

* feat(i18n): enable Indonesian locale in app language config

* test(i18n): remove redundant supported-languages test

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

Bump deps

Fix expense details amount color #658

Fix #631: respect user and group default currency when creating expen…

…ses (#647)

* fix: respect user and group default currency when creating expenses

Closes #631

The expense form always defaulted to USD regardless of the user's or
group's configured default currency. The user/group defaults were
fetched but never applied to the form's currency field.

Changes:
- src/pages/add.tsx: set currency from user.defaultCurrency for
  non-group expenses, and from group.defaultCurrency (falling back to
  the user's) when entering a group context. The setCurrentUser effect
  is gated on router.isReady so the first render (before Next.js
  populates router.query) does not falsely treat a group page as a
  non-group page and apply the wrong default.
- src/store/addStore.ts: resetState now restores the user's default
  currency on unmount so navigating away and back lands on the correct
  default instead of stale state.

Disclaimer: parts of this change were drafted with the help of
Claude Opus 4.7.

* fix: apply full currency preference chain in add expense

Address review feedback on #647: prefer the user's last-used currency
(User.currency) before falling back to the group default and the user's
defaultCurrency setting. Also drop the currency override in resetState
so that resetting the form keeps the last-used currency.

Preference chain when initializing the add-expense page:
  1. currentUser.currency (last used)
  2. group.defaultCurrency (when in a group context)
  3. currentUser.defaultCurrency

Disclaimer: parts of this change were drafted with the help of Claude Opus 4.7.

* fix: keep last-used currency in store across remounts

When picking a currency, also update currentUser.currency in the
add-expense store so the preference chain on the next /add mount sees
the just-picked value without waiting for the async next-auth session
update to settle. On mount, the AddPage effect also preserves the
stored currency for the same user id instead of overwriting it with
potentially stale session data.

Disclaimer: parts of this change were drafted with the help of Claude Opus 4.7.

* fix: await session refresh before navigating after expense submit

Replace the previous remount-time currency preservation with a simpler
fix: in the expense submit handler, await the next-auth session update
(which writes the just-picked currency back into the session) BEFORE
navigating away. This guarantees that any subsequent /add mount reads
the up-to-date currentUser.currency without local-store overrides.

Reverts the in-store overwrite from 49b9778 so currentUser in the
add-expense store keeps mirroring the session user as-is.

Disclaimer: parts of this change were drafted with the help of Claude Opus 4.7.

fix(LanguagePicker): use the language-specific empty-state key (#642)

The 'No language found' placeholder did not exist (#635). The component
looked up account.change_language_details.no_currency_found, which is
not defined in the language sub-tree, so the picker rendered the raw
i18n key when a search filter matched nothing.

Switch the lookup to account.change_language_details.no_language_found
and add the matching English string. Other locales pick this key up
through the existing Weblate flow.

Closes #635

Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com>

fix(LanguagePicker): use the language-specific empty-state key (#642)

The 'No language found' placeholder did not exist (#635). The component
looked up account.change_language_details.no_currency_found, which is
not defined in the language sub-tree, so the picker rendered the raw
i18n key when a search filter matched nothing.

Switch the lookup to account.change_language_details.no_language_found
and add the matching English string. Other locales pick this key up
through the existing Weblate flow.

Closes #635

Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com>

Currencies Translations update from Hosted Weblate (#627)

Translated using Weblate (Russian)

Currently translated at 2.1% (6 of 279 strings)

Translated using Weblate (Nepali)

Currently translated at 100.0% (279 of 279 strings)

Translated using Weblate (Nepali)

Currently translated at 100.0% (279 of 279 strings)

Translated using Weblate (Nepali)

Currently translated at 100.0% (279 of 279 strings)

Translated using Weblate (Dutch)

Currently translated at 2.5% (7 of 279 strings)





Translate-URL: https://hosted.weblate.org/projects/splitpro/currencies/ne/
Translate-URL: https://hosted.weblate.org/projects/splitpro/currencies/nl/
Translate-URL: https://hosted.weblate.org/projects/splitpro/currencies/ru/
Translation: SplitPro/Currencies

Co-authored-by: Angel Pandey <angelpandey2014@gmail.com>
Co-authored-by: Bram Wijkens <madlynbeasly@gmail.com>
Co-authored-by: Ivan Zarubin <avaniar3@gmail.com>

Workaround for _app server side props not working

Also declare the arg and narrow down the scope of variables

Add ability to change settlement date