feat: sync with local plugin status in store#733
Merged
TrainDoctor merged 6 commits intoSteamDeckHomebrew:mainfrom Jan 2, 2025
Merged
feat: sync with local plugin status in store#733TrainDoctor merged 6 commits intoSteamDeckHomebrew:mainfrom
TrainDoctor merged 6 commits intoSteamDeckHomebrew:mainfrom
Conversation
Avoids unneeded re-renders. See https://react.dev/learn/you-might-not-need-an-effect#caching-expensive-calculations
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 SteamDeckHomebrew#360
alvaro-cuesta
commented
Dec 24, 2024
TrainDoctor
added
enhancement
alvaro-cuesta
commented
Dec 24, 2024
TrainDoctor
requested review from
a team and
AAGaming00
and removed request for
a team
alvaro-cuesta
commented
Dec 25, 2024
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.
AAGaming00
approved these changes
Jan 2, 2025
Member
AAGaming00
left a comment
AAGaming00
left a comment
There was a problem hiding this comment.
code lgtm, haven't tested myself but this looks really nice
TrainDoctor
approved these changes
Jan 2, 2025
Member
TrainDoctor
left a comment
TrainDoctor
left a comment
There was a problem hiding this comment.
Evaluated functionality, works great. Merging to main so users can give this a whirl on pre-release.
4 tasks
chenx-dust
pushed a commit
to chenx-dust/decky-loader
that referenced
this pull request
Dec 22, 2025
* 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 SteamDeckHomebrew#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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please tick as appropriate:
Description
This fixes issue: #360
Adds some quality-of-life changes to the plugin store browser:
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.