Automated Drupal 10 compatibility fixes

It would be really great if this could be merged and deployed as a new minor release version, as the ONLY thing needed is a change to the .info file.

I created an issue fork, but I'm not sure if I can do anything with it from there.

It would be great if the PR above could be merged.

+1 for MR1.

Any chance we could get this in a module release?

It's unfortunate there isn't a release for this. For now in my composer.json I have this under the require key:
"drupalcode/block_type_templates": "3286293",

And then under repositories, I have this:

        {
            "type": "package",
            "package": {
                "name": "drupalcode/block_type_templates",
                "version": "3286293",
                "type": "drupal-module",
                "source": {
                    "url": "https://git.drupalcode.org/issue/block_type_templates-3286293.git",
                    "type": "git",
                    "reference": "3286293-6"
                }
            }
        }

Or you could skip this module completely if you just add this code to your THEMENAME.theme file.

Then use block--bundle--block-name.html.twig as your template name.

/**
 * Implements hook_theme_suggestions_HOOK_alter() for form templates.
 * @param array $suggestions
 * @param array $variables
 */
function YOURTHEMENAME_theme_suggestions_block_alter(array &$suggestions, array $variables) {
  // Block suggestions for custom block bundles.
  if (isset($variables['elements']['content']['#block_content'])) {
    array_splice($suggestions, 1, 0, 'block__bundle__' . $variables['elements']['content']['#block_content']->bundle());
  }
}

Thanks, this gets close, but not all the way there. For one thing, I noticed that I needed to use block__block_content_ instead of block__bundle__ to keep my existing template suggestions the same between the module and this custom theme hook.

One issue is that the previous hooks, provided by the module output this:

   * block--block-content-BLOCK_NAME--full.html.twig
   x block--block-content-BLOCK_NAME.html.twig
   * block--block-content.html.twig
   * block--block-content.html.twig
   * block.html.twig

But the custom hook in this example misses the display type template (--full).

vs.

   * block--block-content.html.twig
   x block--block-content-BLOCK_NAME.html.twig
   * block--block-content.html.twig
   * block.html.twig

I'm not actually using the display mode for any of my templates, so losing this suggestion seems ok for my uses, but wanted to point this out in case it affects other's use cases.

Here is what I'm using currently:

/**
 * Implements hook_theme_suggestions_HOOK_alter() for form templates.
 * @param array $suggestions
 * @param array $variables
 */
function YOURTHEMENAME_theme_suggestions_block_alter(array &$suggestions, array $variables) {
  // Block suggestions for custom block bundles.
  if (isset($variables['elements']['content']['#block_content'])) {
    array_splice($suggestions, 1, 0, 'block__block_content_' . $variables['elements']['content']['#block_content']->bundle());
  }
}

AstonVictor → closed merge request !1

It's a duplicate of 📌 D10 compatible version RTBC