summaryrefslogtreecommitdiff
path: root/frontend/src/utils/TranslationHelper.tsx
AgeCommit message (Collapse)Author
2025-01-02feat: sync with local plugin status in store (#733)v3.1.0-pre1Álvaro Cuesta
* 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.
2024-05-25Custom error handler and some misc fixesAAGaming
2023-05-30Missed a toaster for the react toolsMarco Rodolfi
2023-05-27Unified translation classes, fixed missing toaster translation and improved ↵Marco Rodolfi
the error styling report.