This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 13th to Sunday 19th of January 2020.
There is a lot of things going on this week !
The first one is obviously about PrestaShop 126.96.36.199 being available. This maintenance release fixes 16 issues reported on versions 188.8.131.52, 184.108.40.206 and 220.127.116.11. Please read the release note for more informations.
Secondly, we have created the
1.7.7.x branch which will carry the changes being released with 18.104.22.168. So from now on, the work carried out on
develop branch will be released with 1.7.8.
Finally, after asking you what was your opinion about no longer committing generated files and receiving positive feedback for the change, we have implemented it into the develop branch. We have also updated the developer documentation accordingly in order to provide developers with all the necessary information to be able to generate these files on their own.
A quick update about PrestaShop’s GitHub issues and pull requests:
- 73 new issues have been created in the project repositories;
- 48 issues have been closed, including 9 fixed issues on the core;
- 66 pull requests have been opened in the project repositories;
- 71 pull requests have been closed, including 41 merged pull requests.
Code changes in the ‘develop’ branch
- #16964: Refactor UI kit form theme and apply it to the Performance page, by @eternoendless
- #16961: Remove useless customer query filter statements, by @matks
- #17183: Sanity tests - Fix CRUD standard product with combinations test . Thank you @nesrineabdmouleh
- #17150: Functional tests - Fix disable shop function, by @boubkerbribri
- #17129: Functional tests - Set FR text value for custom maintenance text. Thank you @nesrineabdmouleh
- #17086: Functional tests - Crud customer address. Thank you @nesrineabdmouleh
- #17028: Behat tests for Customer, Address features handlers. Thank you @tdavidsonas88
- #15431: Add Money unit test, by @matks
- #17221: Merge 1.7.7.x into develop - 17/01/2020, by @matks
- #17192: Merge 1.7.7.x into develop - 15/01/2020 - again, by @matks
- #17184: Merge 1.7.7.x into develop - 15/01/2020 , by @PierreRambaud
Code changes in the ‘1.7.7.x’ branch (for v22.214.171.124)
- #17229: Recompute FOSJSRouting JSON file, by @matks
- #17175: Replace partialRefund form/builder/dataProvider with CancelProduct, by @matthieu-rolland
- #17169: Refacto partial refund handler, by @jolelievre
- #17202: Functional tests - Add numbers for all directories. Thank you @nesrineabdmouleh
- #17201: Functional Tests - Fix “emailThemes/01_previewEmailThemes” test. Thank you @nesrineabdmouleh
- #17168: Functional tests - Fix test customer bulk action, by @boubkerbribri
- #17167: Functional Tests - Fix Enable Disable shop automated test, by @SimonGrn
- #17155: Refacto refund, by @jolelievre
- #17154: Functional tests - Fix test employee and maintenance, by @boubkerbribri
Code changes in the ‘1.7.6.x’ branch (for v126.96.36.199)
Code changes in modules, themes & tools
Changes in developer documentation
- #444: Add link to “why github flow is complex” article, by @matks
- #443: Add MySQL default credentials. Thank you @gadnis
- #442: Fix typo in tabs.md, by @Quetzacoalt91
- #440: Provide github tuto links to contribute, by @matks
Core Weekly Generator tool
Faceted search module
Prestashop UI Kit
- #84: Improve Inputs, by @NeOMakinG
- #76: Improve cards, by @NeOMakinG
- #71: Add default ps-dropdown and adjust other dropdown elements, by @NeOMakinG
Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @matks, @SimonGrn, @nesrineabdmouleh, @PierreRambaud, @matthieu-rolland, @sam-pires, @jolelievre, @boubkerbribri, @gadnis, @Quetzacoalt91, @atomiix, @LouiseBonnard, @tdavidsonas88, @eternoendless, @NeOMakinG, @mickaelandrieu!
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!