Spent 3 nights in Ghent and was woken up by the sun every day. Had a couple of beers and good conversations with the fine folks around @drupalbe. Finally at the train station literally bumped into @wimleers on his way back from #drupalcon Portland. Thanks @Klara, @borisson_ and their team for organizing this edition of #drupalcamp Ghent.
@wimleers@drupalbe@Klara@borisson_ I've just arrived in my city when a child in the next compartment says: "Look at this weather, I'd rather have stayed in Belgium."
I often had to grep through *.services.yml to figure out whether a certain service uses periods or underscore in its id. I simply cannot remember if its config.factory or config_factory. I just realized there is a better way to reference services thanks to autowire aliases! I just use '@\Drupal\Core\Config\ConfigFactoryInterface'. And in PHP code (e.g. classes implementing ContainerInjectionInterface) I'm now using ConfigFactoryInterface::class instead of the string literal.
Anyone else enjoying their disillusionment that upgrading major #Drupal versions became easy as of Drupal 8?
The pain involved in the Drupal 8 to 9 upgrade was expected to just part of the learning curve of adopting a new system. It's supposed to get easier... isn't it?
My Drupal 9 to 10 upgrade for one of my larger sites is so painful that I'm now going to seriously consider going to Backdrop for some of my remaining Drupal 7 sites instead of upgrading them to Drupal 10.
BTW, I'm not dumping on the Drupal 8+ system as a whole. I actually love it and will keep building on it. It's just that the smaller sites I've done would not have the budget for me to engage in this exercise every 2 years nor would I have the time to pray to the migration gods for so many sites like this.
@sysop408 The lenient plugin only acts on dependencies which were explicitly specified using an allow list via composer.json extra data. That only helps when its clear which dependency is causing the mess. This doesn't seem to have been the case in your situation.
Test discovery works completely different depending on whether a path is specified on the phpunit command line or not. If a path is specified, the given directory is searched recursively. Without path, tests are discovered from the testsuites dictionary in phpunit.xml.
I used to specify a path on the phpunit command line as a quick way to limit what tests are executed. I'm going to use --group and --filter from now on in order to avoid mistakes like the one corrected by https://www.drupal.org/i/3393072
@kreynen@rachel_norfolk git fame would be nice too. Often git blame just doesn't feel right. Especially when tracing the origins of a nice piece of code.
@pcambra@benjifisher I wouldn't recommend that in general. It could simplify the transition for a site which has only a few admin accounts. But if you have lots of users, a hard reset might lead to an unfortunate spike of customer support requests. 😓