Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request] Identify and index plugins by package name, not plugin name #571

Open
3 tasks done
wheaney opened this issue Dec 19, 2023 · 0 comments
Open
3 tasks done
Labels
feature request a request for a feature, no guarantee of addition

Comments

@wheaney
Copy link
Contributor

wheaney commented Dec 19, 2023

Please confirm

  • I have searched existing issues
  • This issue is not a duplicate of an existing one
  • This is not a request for a plugin

Feature Request Description

I recently tried to "rebrand" my plugin by changing its name (as defined in plugin.json's name property) and it created a duplicate plugin in the store. It's been a couple months since I tested this, so I'm not 100% certain anymore, but I think it also would prevent decky from detecting that there's an update for an installed plugin, because it would treat it as a new plugin. In contrast to this, the installation process creates a plugin directory based on the package name (or repo name, not sure which), so I believe it wouldn't install as a second plugin because it would overwrite the old one. This package name should be used to uniquely identify the plugin throughout the whole stack, allowing devs to rename a plugin and still get a smooth update experience for existing users.

Further Description

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request a request for a feature, no guarantee of addition
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant