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

Feature Request: Ability to Update Addon URL with Configuration #271

Open
vanchaxy opened this issue Apr 8, 2024 · 1 comment
Open

Feature Request: Ability to Update Addon URL with Configuration #271

vanchaxy opened this issue Apr 8, 2024 · 1 comment

Comments

@vanchaxy
Copy link

vanchaxy commented Apr 8, 2024

Currently, addon URLs are used to identify the addon. While this allows the installation of multiple instances of the addon, it doesn't allow users to update the addon configuration without reinstalling the old one. It would be great to have the ability to update the addon with a different addon URL (e.g., using an ID).

For example, such a feature should allow users to update the URL like this:

I propose one of the possible solutions:

a) Add a new property to the manifest, something like "only_one_installation_allowed: true".
b) If a user tries to install such an addon and the same ID is already installed, show them a warning ("You are going to uninstall addon ...").
c) Show an additional warning if the domains of the old and new addons do not match.

This functionality would only be applicable to uninstallable addons, ensuring that no one could install the default "com.linvo.cinemeta" addon.

I have found a similar issue but it doesn't work for me. Also, the requested feature could work within the same version installation. (e.g. for temporary auth token updating or catalog list configuration).

@vanchaxy
Copy link
Author

vanchaxy commented Apr 8, 2024

@sleeyax comment from discord:

Another approach would be a system where the first dev to use a particular id "claims" it. It becomes unique and unavailable until the addon gets removed from the community catalog. In doing so the ownership logic is shifted and you can use whatever domain you like.
Thinking about it I'm not sure what the exact purpose of the id field actually is atm. Maybe I'm missing something obvious.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant