| Age | Commit message (Collapse) | Author |
|---|
|
* Translated using Weblate (Italian)
Currently translated at 100.0% (176 of 176 strings)
Translation: Decky/Decky
Translate-URL: https://weblate.werwolv.net/projects/decky/decky/it/
* Translated using Weblate (English)
Currently translated at 100.0% (176 of 176 strings)
Translation: Decky/Decky
Translate-URL: https://weblate.werwolv.net/projects/decky/decky/en/
* Translated using Weblate (Italian)
Currently translated at 100.0% (176 of 176 strings)
Translation: Decky/Decky
Translate-URL: https://weblate.werwolv.net/projects/decky/decky/it/
---------
Co-authored-by: Marco Rodolfi <marco.rodolfi@tuta.io>
|
|
|
|
* fix: useDeckyState proper type and safety
* refactor: plugin list
Avoids unneeded re-renders. See https://react.dev/learn/you-might-not-need-an-effect#caching-expensive-calculations
* feat: sync with local plugin status in store
Adds some QoL changes to the plugin store browser:
- Add ✓ icon to currently installed plugin version in version selector
- Change install button label depending on the install type that the
button would trigger
- Adds icon to install button for clarity
The goal is to make it clear to the user what the current state of the
installed plugin is, and what would be the impact of installing the
selected version.
Resolves #360
* lint: prettier
* fix: add missing translations
* refactor: safer translation strings on install
Prefer using `t(...)` instead of `TranslationHelper` since it ensures
that the translation keys are not missing in the locale files when
running the `extractext` task.
By adding comments with `t(...)` calls, `i18next-parser` will generate
the strings as if they were present as literals in the code (see
https://github.com/i18next/i18next-parser#caveats).
This does _not_ suppress the warnings (since `i18next-parser` does not
have access to TS types, so it cannot infer template literals) but it at
least makes it less likely that a translation will be missed by mistake,
have typos, etc.
|
|
i can't wait to fix the weblate conflicts this one causes
|
|
The static files need to be inside the module to be installed correctly
as part of the module.
|
