Replies: 1 comment
-
Concerning cookiecutter, I totally agree and would be happy to see it done! (also this part is duplicate of #14 ) Concerning the plugin registry: that also would be nice, down the road. But obviously it would only make sense when the plugin ecosystem actually starts to grow. I will keep this issue open for the plugin registry aspect. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Just to document some ideas:
That the creation of all plugins goes as follows:
Project layout and structure done, entry point and everything done. (It could also ship with some basic tests of needed stuff to work properly and a setup CI and enforce so a certain level python.)
Now we only need a tutorial on how to actually implement the thing and not so much the stuff around.
A cutter could be connected to a helper tools, i.e I provide an external schema, the cutter gives me some implementation skeleton, which I just have to adapt.
What do you think? I would volunteer to do it, if I get the task to create some plugins I will probably even save time doing the template.
Beta Was this translation helpful? Give feedback.
All reactions