A survey of some site link checker tools. Do you know another one? Preferably one that could be used in a CI environment?
Hey, Drupal 8.8.0 has a defined Composer behavior!
That's right, Drupal 8.8.0 is Composer-first. That means you can build it from an official, signed-off-by-maintainers type Composer project template. You can do this:
$ composer create-project drupal/recommended-project:^8.8.0 my_web_directory
This is a big deal because previously you had to use a third-party Composer project template to be able to build a codebase that didn't completely misunderstand you when you subsequently typed:
A Diverse Drupal Community Needs Composer
The Drupal community has been trying to come to terms with modern build tools for a while.
We have Drupal core which is managed with Composer, but we also have contrib modules and some of them want to use Composer, too.
The canonical example is Address module. It requires an external PHP library, necessitating the use of Composer to add it to the codebase.
At least, that's the thought.
Why does Mile23 keep going on about symfony/phpunit-bridge in the Drupal issue queues?
Let's find out.
This is a deep-ish dive into how PHPUnit isolates tests, and might give some clue as to how many moving parts are involved.
Here are some ideals I'd like to see in Drupal core development:
- There is a process by which the quality of Drupal can improve.
- Non-coders can participate in planning.
- Maintainers have a well-understood reason for saying, "No."
- Everyone can do a better job of estimating their real level of participation in core development.
- Time is structured such that we respect the time and effort of others.
I want to talk about that last one: Everyone's time and effort is valued.
Join me as I try to remember all the things I learned at DrupalCamp LA 2015...
I just gave a talk at DrupalCamp LA, entitled 'Inventing The Container.'
Here are the slides as PDF.
You need Drush.
I need Drush to work on Pantheon. Pantheon's documentation states that they only support Drush 5, and since it's not my data I'm managing but my clients', that's what I have to use.
In fact, it's annoying to work with Drush. That is, the magic stuff it does when you use it isn't annoying and is quite useful. But keeping all the versions you need for all the different use-cases is what's quite annoying.
So I gave a talk at San Diego Drupal Camp (SANDCamp) and Midwest Drupal Camp (MidCamp) 2015. It was called 'PHP Code Analysis Through Unit Testing.'
The MidCamp page is here: http://2015.midcamp.org/session-proposal/php-code-analysis-through-unit…
It has a link to the video recording: https://youtu.be/ebygSeVz5vQ
Just a heads-up of a proof-of-concept I did.
Here's a github repo for the page_example module from examples. I've added a
composer.json file which requires
symfony/console (arbitrarily), and
composer/installer (to make it work): https://github.com/paul-m/composer-drupal-module
I then made a packagist.org entry for it: https://packagist.org/packages/mile23/page-example