Voir mes commentaires

la docstring ne suit pas le formalisme que nous cherchons à appliquer (oui je sais pour l'instant c'est très incohérent partout mais comme là c'est du refacto c'est l'occasion) :

        """Get user filters as a lower str list.

        :param lower: To tell if we want the list as lowercase, defaults to False
        :type lower: bool, optional

        :return: _description_
        :rtype: list[str]
        """

Je te laisse compléter la description du retour.

Si tu utilises VS Code une extension recommandée permet de prégénérer la structure. Chez moi le raccourci est crtl+shift+2

ligne commentée ?

yeah, see my above comment. More straight forward: read it from requirements.txt in __about__.py to expose it.

Just avoid the hammer since it's the historical icon of Plugin Builder https://plugins.qgis.org/plugins/pluginbuilder3/

Thanks, those first proposals look good :). My order of preference: 5, 4, 3.

Just a though: the plugin's purpose is about to create/initiate a new plugin project and here, I feel like we don't have this idea of creation. Do you get what I mean?

Based on: template-qgis-plugin!103

Ju M (1dda12f2) at 16 Mar 18:42

Ju M (89b96d7d) at 16 Mar 18:23

... and 6 more commits

Well it was not for requirements but for plugin_dependencies: template-qgis-plugin!89 (diffs)

Avoid the cookiecutter version number hardcoded. Use the __about__ module to read it from metadata.txt. Hint: I've done that recently.. but I can't remember where ;)

FYI @sbeorchia we aim to broadcast this plugin at https://conf.qgis.osgeo.fr/ next week

Ju M (1f5ee91d) at 16 Mar 18:01

Ju M (36af05bf) at 16 Mar 17:58

Ju M (d48f02a5) at 16 Mar 17:40

Ju M (4264a4e4) at 16 Mar 17:40

... and 1 more commit

Ju M (34424c20) at 16 Mar 17:40

... and 8 more commits