Drupal Code Search now index recipes

Made it easier to get a list of projects that are included in a particular recipe. It's thanks to the sponsorship of Vardot, and previously Palantir.net that I'm able to spend time on tooling for the community. Many thanks to them.

Code search:

  • The API and Search now index recipes and some general projects.
  • On the Search interface you'll see a new icon on modules that belongs to the Drupal CMS dependency chain (clear your browser caches to see it if you've already visited).

I'm not super sure about the general projects reaching the search index, tell me if it's too noisy in the results. 

Code Query API:

  • In the API you'll be able to query the list of project by recipe membership. Want to know all the projects in Drupal CMS? or 
  • The change record data was also a bit out of date on some older module branches, the bug has been fixed and the counts have corrected a bit. 

drupal-patch-check composer plugin:

Install on your Drupal project with 

$ composer require --dev tresbientech/drupal-patch-check
  • You can now add patches with drupatch:add <issue URL, MR url>, a new --drop-tests removes the tests from the patch since  the Drupal 12 release will ship without the tests files.
  • To help vendor patches in use the drupatch:pin command, it'll make it possible to reroll and remove tests from MR urls, to update the patch you can use drupatch:pin --refresh and it'll fetch the MR with the latest changes to apply.
  • Added a command to migrate from cweagans/composer-patches:1.x to 2.x, it's stricter in the patches it can apply by default but it's better for predictability, and the plugin will help reroll clean patches. See what it would take to update your project by running: drupatch:upgrade-patch-manager --dry-run

I've been thinking about making a post about what drupal.org should provide from this API. Having the drupal.org database easily reacheable would be a blessing for some tasks and avoid an imperfect and limited data crawl. It's still run from a cupboard but I seriously upgraded the hardware for it. The services run on a modern CPU, 64GB ram, so capacity is not an issue anymore for the time being. Based on server logs, search is the clear winner. What else do you think should be part of the drupal.org api?