-
Notifications
You must be signed in to change notification settings - Fork 61
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
Add support for renaming plugin package_name #271
Add support for renaming plugin package_name #271
Conversation
I'm not sure to understand, is-it a feature to update the plugin name ? Did you try to check the behavior in QGIS desktop ?
Sorry if it's not related and skip my comment :) Edit : |
Hi @Gustry , sorry I should make this PR as a draft since it’s not ready to review yet. |
Ok thanks for the information. You can still press the "convert to draft" ;-) There are few things to check indeed for allowing this ticket. I'm not sure how you want to proceed on the desktop side. |
It would be enough for this time to keep (old) plugin identifier (directory name) and only change human readable name, likely with no changes in qgis desktop. Renaming would effectively forcing new human readable name. Human readable name should be used in QGIS installer, and also on qgis plugin site in title of the plugin/list of plugins. Important is to now override this human readable name on new plugin version upload (as zip) - this name should be configurable ideally as plugin admin/owner in the part where you upload new plugin version. It would be even enough it it is not modifiable by user/owner , just by some super-admin (e.g. need to write mail to Tim to change the name for us) Thanks a lot! |
Thanks @PeterPetrik . @Xpirix when you take over the original ticket and this PR it might be good to write up a clear design for @PeterPetrik and @Gustry to comment on before you start building stuff, taking special care to understand and document the impacts in the QGIS desktop environment. |
Thanks @timlinux . That is well noted. |
@PeterPetrik @Gustry @timlinux Please find below my understanding of the ticket and the PR.
Please feel free to comment if you have any concerns about this. EDIT: If the maintainer uploads a new version with a non-matching name, it will raise an error. In the plugin properties page, there will be a checkbox that will allow the django admin to 'allow name in metadata.txt to update the plugin name' as mentionned in #270 . If this option is checked, the name/title of the plugin in the website and in QGIS will change depending on the value in metadata.txt. |
Looks good to me, maybe @wonder-sk can comment too? |
Looks good to me as well. I agree that it is best not to allow modification of package name (at least for now) as this would introduce issues on the client side related to the renaming and how to smoothly handle the transition. |
Thanks @PeterPetrik @wonder-sk . Please find below a new PR for this: |
This is for #270