Work completed in the last couple of weeks
Recently we’ve been working on improving our work efficiency through automation - as a follow-up to the automated patch releases mentioned in the previous update post, we’re trialing automated merge-ups on the silverstripe/framework repository. We’ve validated that our approach for automated patch releases works well, so we’ll be looking at rolling that out across all supported modules soon.
Following the CMS 5 release, we’ve revisited our JavaScript linting rules which should improve the quality of the JavaScript code in our supported modules, making it easier to maintain.
We’ve also made a bunch of incremental improvements to the new eager loading functionality that will be released in silverstripe/framework 5.1.0, and of course we’ve fixed a bunch of bugs. Some specific highlights are listed below.
Bug fixes and other immediate changes
- Predicated query results cannot be iterated over multiple times patched in 5.0.9 of silverstripe/framework
- Move CMS 4 supported module list to developer doc to align with CMS 5
- Error when previewing page and asset doesn’t exist patched in 1.13.3 and 2.0.4 of silverstripe/assets
- HTML showing in inline preview patched in 3.0.2 of silverstripe/elemental-fileblock & silverstripe/elemental-bannerblock
Changes to look forward to in future releases
Community pull requests merged
As always we greatly appreciate community contributions which help make Silverstripe CMS better for everyone. The following community pull requests have been merged recently:
- Add new ListboxField react component by Andrew Paxley
- avoid multiple calls to records->count() In PermissionCheckboxSetField by Thomas Portelange
- use orm cache in LoginSession by Thomas Portelange
- use orm cache in SessionManagerField by Thomas Portelange
- Removed references to Zend_Translate in i18n docs by Anthony Thorpe
- Add new OnlyTheseMembers Inherited Permission type by Andrew Paxley
Focus for the next couple of weeks
Coming up, we’ll be keeping an eye on auto merging on the framework repository - all going well that will get rolled out across all of our supported repositories. We’ve got some more incremental enhancements we want to make to the eager loading functionality before we release it, some potential performance enhancements, and we’re looking at an automated way of keeping some of our module files standardised.