We should provide some reference modules that people can use as an example/reference/skeleton to build their modules.
Usecases I can think of:
These modules should provide:
We should update them for every minor version releases, in order to show new useful features for modules. So for 1.7.6 we should use Twig, Doctrine, new hooks, tests.
Doc tutorials about modules should refer to them
Cc @Matt75 馃槈
This is something that @tomas862 had already started. https://github.com/Invertus/prestashop-module-skeleton
Great 馃コ
We will have some feedback during PSD Paris to define priority depends on top watchers.
For Payment Module, there are already https://github.com/PrestaShop/paymentexample who need some improvement to fit guideline defined here.
For Carrier Module, we have to explain how FrontController::registerJavascript()
and first argument can help to not have multiple Google Maps included for example. Recurring problem since beginning of PrestaShop 馃槄
I think we should have something like PrestaShop\PrestaShop\Core\Payment\PaymentOption
for Carrier, because some needs to select a pickup store etc... Currently this process is a real mess in order process due to missing guidelines...
Also, there is the validator which is able to generate modules: https://validator.prestashop.com/generator, and this old repository in which we can find another skeleton (from 2014): https://github.com/PrestaShop/module-generator
It looks like everybody had the same idea, but it is now time to merge everything in a single place instead of creating something else new. :)
Let me know if I can help.
Most helpful comment
Also, there is the validator which is able to generate modules: https://validator.prestashop.com/generator, and this old repository in which we can find another skeleton (from 2014): https://github.com/PrestaShop/module-generator
It looks like everybody had the same idea, but it is now time to merge everything in a single place instead of creating something else new. :)
Let me know if I can help.