Drupal's Batch API is great, it allows you to easily perform long running processes with feedback to the user.
But during Drupal 8's development processes it was one of the remaining systems that didn't get the full object oriented, service-based architecture.
Much of the batch API is largely unchanged from Drupal 7.
But that doesn't mean you can't write unit-testable callbacks.
Let's get started.
This one tripped me up on a recent Drupal 8 project.
Easy to miss when you're working in a development oriented environment with things like JavaScript preprocessing turned off.
A JavaScript file was being added just fine with aggregation turned off, but not getting added with it turned on.
On a recent Drupal 8 client project our client was building listing pages using views exposed filters and adding these to the menu.
This resulted in several menu URLs pointing to the same base path, but with the query arguments determining the difference.
However Drupal 8's default menu-trail calculation was resulting in the menu highlighting all instances when one of them was viewed.
Luckily the active trail calculation is done in a service and it was simple to modify the default behaviour.
Read on to see how we did it.
Whilst working on a Drupal 8 project, we found that cache tags for a Block Content entity embedded in the footer weren't bubbling up to the page cache.
Read on to find out how we debugged this and how you can ensure this doesn't happen to you too.
Earlier in the year we worked with a household Australian name to help them build a next-generation more-performant version of their energy-comparison site.
We used Blackfire.io to optimize the critical elements of the site.
Read on to find out more about our experience.
Drupal 8 comes with a services based architecture allowing clean dependency injection, separation of concerns and another way to modify how Drupal works without hacking core
You've probably heard that Drupal 8 lets you swap out a core service for your own implementation, hey, I even said it myself here and here, but how do you achieve that?
Read on to find out how to manipulate Drupal 8 services at run-time and how this compares to other popular PHP Frameworks like Laravel, Silex and Symfony
Drupal 8 comes with two extension points for module developers to allow other modules to interact with their code.
The trusty alter hook, the linchpin of Drupal versions past is still there - allowing other modules to interact and intervene in the behaviour of your module.
But there is a new kid on the block, the event system.
So as a module developer how do you decide whether to use the alter system or the event system.
During this weeks developers' meeting our lightning talk was all about Drupal 8's ThirdPartySettingsInterface.
Here's the video introduction to this powerful new feature in Drupal.
During our weekly developers meeting I spoke about my approach to contributing to Drupal core, sharing some tips and tricks I've learnt along the way
This is a preview of a proposed session for DrupalSouth Melbourne 2015