PrestaShop Core Weekly - Week 01 of 2019
An inside look at the PrestaShop codebase
This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the first week of the year, from Monday 31st of December 2018 to Sunday 06th of January 2019.
General messages
Dear Developers,
First week of 2019 is a good start with 31 merged pull requests. But now that everybody is back, let’s continue to contribute like the best weeks of 2018, and aim at minimum 40 pull request merged per week. That would be great! And remember, a small pull request, solving one problem, is easier to review and to merge than a very big one with changes in a lot of files and/or about many issues.
Since the beginning of the year, I have improved the first section of the core-weekly, with new figures about the PrestaShop project repositories on GitHub. In a few week, with a bit of history to show, I will try to share a chart so we can look at the trends.
A quick update about PrestaShop’s GitHub issues and pull requests:
- 36 new issues have been created in the project repositories
- 43 issues have been closed, including 11 fixed issues
- 66 pull requests have been opened in the project repositories
- 40 pull requests have been closed, including 31 merged pull requests
Code changes in the ‘develop’ branch (for v1.7.6.0)
Core
- #11985: PHP unit test case static method calls. Thank you @MathiasReker
- #12010: Make filtering of LazyArrays return a new instance, by @eternoendless
- #12015: fix typo in example nginx config file. Thank you @mwht
Back office
- #10774: Migration of “International > Localization > Currencies” page listing. Thank you @tomas862
- #11481: Add cover & menu thumbnail images deleting for category. Thank you @sarjon
- #11723: Migrate customer Add/Edit actions. Thank you @sarjon
- #11922: Fix searching issue in the Credit Slips page, by @khouloudbelguith
- #11932: Can’t sort tax included for now, by @PierreRambaud
- #11936: Description has a max length and can not exceeded, by @PierreRambaud
Front office
- #10294: Fix minimum order amount for secondary currency. Thank you @sadlyblue
- #10297: Fix image dimensions in Product Card view. Thank you @CaptainYouz
- #10487: Added breadcrumb to the manufacturers pages. Thank you @SebBareyre
- #11726: Force dni fields required if associated Country needs it, by @jolelievre
- #11754: Fix wrong discount details on order page / on invoice, by @tomlev
Tests
- #10477: Added an Error Data Listener, by @mickaelandrieu
- #11898: Fix travis script for running tests and fix broken tests, by @matks
- #12001: Filters in catalog page. Thank you @ansar21mallouli
- #12007: Delivery slip test. Thank you @YosraAk
- #12013: Isolate legacy tests into suites to fix develop branch, by @matks
Code changes in the ‘1.7.5.x’ branch (for v1.7.5.1)
Install
- #11937: Check if intl is installed in installer, by @PierreRambaud
Code changes in modules, themes & tools
Docker
- #150: Add libzip package to the base image, by @Quetzacoalt91
- #151: Allow all languages to be installed with PrestaShop , by @Quetzacoalt91
Circuit Breaker
- #2: Added exemple of use, by @mickaelandrieu
- #3: Introduced CB factory, by @mickaelandrieu
- #4: Make the creation of places more robust, by @mickaelandrieu
- #5: Introduced transaction and storage, by @mickaelandrieu
- #7: Fixed typo, by @mickaelandrieu
- #8: Implement Transaction + Storage, by @mickaelandrieu
- #10: Added unit tests for Storage, Transaction and Assert classes, by @mickaelandrieu
European VAT number
Changes in Documentation
Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @ansar21mallouli, @borlum, @CaptainYouz, @MathiasReker, @mwht, @sarjon, @sadlyblue, @SebBareyre, @tomas862, @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!