blog-posts Posted October 8, 2019 Share Posted October 8, 2019 This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 9th of September to Sunday 15th of September 2019. A quick update about PrestaShop’s GitHub issues and pull requests: 72 new issues have been created in the project repositories; 64 issues have been closed, including 8 fixed issues on the core; 72 pull requests have been opened in the project repositories; 64 pull requests have been closed, including 8 merged pull requests. Code changes in the ‘develop’ branch Core #15518: Update README, by @matks #15447: Re-enable port in shop domains, by @matks #15340: Update minimum compatibility to PHP 7.1.3, by @eternoendless Back office #15429: Fix Add an Employee Handler with int casting required, by @matks #14925: Copy images from SCSS directory to public for the new-theme (to improve the release ZIP), by @Progi1984 Tests #15519: Fix Close browser after each scenario, by @boubkerbribri #15509: Remove the smoke tests campaign - Puppeteer . Thank you @nesrineabdmouleh #15470: Add Checkout FO to Sanity tests puppeteer, by @boubkerbribri #15421: Cart FO tests with puppeteer - Sanity tests campaign. Thank you @nesrineabdmouleh Code changes in modules, themes & tools Faceted search module #141: Repair dev branch, by @PierreRambaud #138: Calculate the number of available products with the stock management, by @PierreRambaud #137: Revert “Calculate the number of available products with the stock management”, by @PierreRambaud #136: Fix wrong filter price, need match shop current. Thank you @alex4102 #135: Use fetch method instead of render to allow override, by @PierreRambaud #132: Calculate the number of available products with the stock management, by @PierreRambaud #130: Add hook for Specifc Prices and move price min and max from rounded integer to decimal, by @PierreRambaud #129: Use p tag instead h1 for filters, by @PierreRambaud Changes in developer documentation #344: Fix bad links and empty index page, by @eternoendless #343: Provide more module examples to get started, by @Quetzacoalt91 #340: Fix a spelling mistake in the doc. Thank you @senkuu #334: Explain how to use Symfony service overrides and decorations, by @matks #329: Added a table that sum up supported Symfony features, by @mickaelandrieu #324: Fix bad link on Grid Actions reference page, by @matks #321: Improve documentation on module translation, by @eternoendless #317: Add precisions for custom hooks. Thank you @jf-viguier #315: Add server parameter to registerjavascript. Thank you @zalexki #288: Improve doc for module’s services.yml file. Thank you @aziule #270: How to add grid actions tutorial, by @mickaelandrieu Block reassurance module #26: Revert “Release 4.0.0”, by @matks #25: Updated Readme & License & Enabled Release Drafter, by @Progi1984 #24: Release 4.0.0, by @Progi1984 #22: Last module tech improvements for v4, by @Progi1984 Classic-rocket theme #94: Add missing classes on product miniatures. Thank you @micka-fdz #93: Remove duplicate on smarty block name. Thank you @micka-fdz #81: Fix padding and margin spacer. Thank you @Kmoulun PrestaShop Specifications #69: Shipping > Carrier > add new/edit. Thank you @samuel-pires PrestaShop Docker images #178: Update mysql-client dep to default-mysql-client, by @Quetzacoalt91 #176: Fix README screenshot image URL, by @matks #175: Release 1761, by @matks Prestonbot #89: Switch dependencies to symfony/symfony instead of symfony/lts, by @matks #87: Add version number API route, by @matks Wire payment module #45: Update module short description, by @colinegin Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @PierreRambaud, @eternoendless, @Quetzacoalt91, @boubkerbribri, @alex4102, @matks, @nesrineabdmouleh, @micka-fdz, @Progi1984, @senkuu, @samuel-pires, @colinegin, @damiandominella, @mickaelandrieu, @Kmoulun, @jf-viguier, @zalexki, @aziule! Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub! If you want to contribute to PrestaShop with code, please read these pages first: Contributing code to PrestaShop Coding standards …and if you do not know how to fix an issue but wish to report it, please read this: How to use GitHub to report an issue. Thank you! Happy contributin’ everyone! View the full article Link to comment Share on other sites More sharing options...
Recommended Posts