| Age | Commit message (Collapse) | Author |
|
|
|
|
|
a time
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
which fixes: #685 (#779)
* fix(Updater): Remove `FocusRing` component and use `Focusable` instead
* feat(Markdown): Add Link `class` to a tag for a mentain a Steam UI colors palette
|
|
* Add Decky branch switcher and updater to error boundary
* Linting fixup
* Update DeckyErrorBoundary.tsx
Allow for plugins to trigger new behavior.
* Lint fixup
|
|
* fix(deps): update @decky/ui to version 4.10.1
* chore(deps): bump @decky/ui 4.8.3 -> 4.10.1
* fix(types): UIMode -> EUIMode
* fix(types): bypass missing type in library.ts
* fix: lint
---------
Co-authored-by: AAGaming <aagaming@riseup.net>
|
|
* Simplify the typing of the plugin URL for the user. Make the http/https prefix optional.
* Fixed the formatting using prettier --write
|
|
* 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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Frontend progress bars
* Backend bit
* closure is stale i think so no closure for you
* Fix formatting of the progress svgs
* Reset progress bar when new plugin starts downloading
|
|
TODO: update package.json to match once @decky/ui is on NPM
|
|
|
|
|
|
|
|
i must have done a great deal of harm in a past life to deserve this mistreatment by formatting tools. why do they hate me.
|
|
|
|
* git no work so manually uploading files :(
* argh i wish git was working
* ok next time i'll make git work
* Update updater.py
* git please work next time this took ages without you
* fix me locales
* Update updater.py
* Update en-US.json
* Update updater.py
* Update updater.py
* i wish my python LSP stuff was working
* fix it
* Update updater.py
* Update updater.py
* Only show testing branch as an option if it is already selected
* Initial implementation for fetching the open PRs. Still need testing and a token to complete this.
* Wrong filter capitalization
* Fix a couple of typos in the python backend updater.
* Fix typos pt 3
* This should be the last one
* Prepend the PR version number with PR- to make it clearer that's the PR number.
* Update prettier to the latest version otherwise it will never be happy with the formatting.
* fix merge mistake
* fix pyright errors & type hint most new code
* fix strict pyright errors...
* not sure why my local linter didn't catch this
* Reimplement the logic between PR and artifact build to limit API calls
* Fix pyright errors
* use nightly.link for downloads
* remove accidental dollar sign
* fix various logical errors. the code actually works now.
* set branch to testing when user downloads a testing version
---------
Co-authored-by: Marco Rodolfi <marco.rodolfi@tuta.io>
|
|
|
|
|