This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 07th to Sunday 13th of January 2019.
Last week, two new repositories have been added to the PrestaShop project on GitHub:
- PhpPsInfo, a tool to check if a server has all Apache and PHP prerequisites before starting to install a PrestaShop online store on it
- Circuit Breaker, a library that allows applications to better handle cases when third party services (payment solutions, solutions using the webservices/API, Addons, …) go offline. It will be progressively introduced in PrestaShop and its modules.
As usual, your feedback is welcome.
A quick update about PrestaShop’s GitHub issues and pull requests:
- 68 new issues have been created in the project repositories
- 45 issues have been closed, including 3 fixed issues
- 62 pull requests have been opened in the project repositories
- 53 pull requests have been closed, including 41 merged pull requests
Code changes in the ‘develop’ branch (for v126.96.36.199)
- #12014: Unify algorithm for calculating average tax rate for products in a cart, by @eternoendless
- #12022: Use Symfony Cache Clear in ModuleManager instead of deprecated Cache …, by @matks
- #12031: Make pre-commit execute linter only if php files have been staged, by @eternoendless
- #12089: Implement AbstractTypedCollection with tests, by @jolelievre
- #12125: Fix bad GridFactory service definition, by @matks
- #11153: Migration of “Catalog > Brand & Suppliers > Suppliers” listing. Thank you @tomas862
- #11693: BO: FIX PrestaShop#9853 Search feature value and pagination. Thank you @studiox3
- #11854: Add customer_message table name into SQL request. Thank you @Klemart3D
- #11877: introduces moved search and reset type button to the right. Thank you @tomas862
- #12052: SERP : Avoid mutating a prop directly + fix url encode, by @PierreRambaud
- #12023: When downloading a virtual good, check if the order was made by the current user.. Thank you @garnele007
- #12030: Filters by category in catalog page. Thank you @ansar21mallouli
- #12045: Update autoupgrade test. Thank you @YosraAk
- #12054: Migrate legacy unit test for Hashing, by @matks
- #12060: Enable PHP CS Fixer on tests folder, by @matks
- #12067: Add some fixes to the campaign full. Thank you @YosraAk
- #12079: fix static cache reset on ObjectModel, by @tomlev
- #12049: Change position, unhook and transplant a module. Thank you @ansar21mallouli
- #12086: Location: zone and country. Thank you @ansar21mallouli
- #12091: Geo-location: By IP address. Thank you @ansar21mallouli
- #12104: Update delete shopping cart test. Thank you @ansar21mallouli
- #12112: Update bulk actions in catalog page test. Thank you @ansar21mallouli
- #12115: Update create manufacturers test. Thank you @ansar21mallouli
- #12122: Add a new brand address test. Thank you @ansar21mallouli
Code changes in the ‘1.7.5.x’ branch (for v188.8.131.52)
Code changes in modules, themes & tools
- #13: Added Symfony Cache support, by @mickaelandrieu
- #16: Added Code coverage information, by @mickaelandrieu
- #17: Rely on PSR-16 adapters of Symfony cache, by @mickaelandrieu
- #18: Covers exceptions with unit tests, by @mickaelandrieu
- #19: Improved SimpleCircuitBreaker class, by @mickaelandrieu
- #20: Improved Composer configuration, by @mickaelandrieu
- #21: Add php qa report, by @mickaelandrieu
- #23: Extracted the Client from SimpleCircuitBreaker, by @mickaelandrieu
- #24: Added Travis CI badge, by @mickaelandrieu
- #25: Added PHPQA Github Action, by @mickaelandrieu
Docker internal images
Search bar autocomplete
PrestaShop Emails SDK
Changes in Documentation
Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @ansar21mallouli, @basjac, @garnele007, @Klemart3D, @idnovate, @matthieumota, @studiox3, @tomas862, @rdy4ever, @YosraAk!
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:
…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!