Problem/Motivation

It seems to be an emerging best practice that, if your site template uses Canvas (and this starter kit does), it needs to be shipping any components (canvas.component.*.yml config files) that are in use in page regions, content templates, patterns, or landing pages.

This is something that's very easy to miss or mess up, and the consequences can be hard-to-debug when there's a version mismatch. Shipping the component entities sidesteps this -- the component versions you use in the site template are the same as the component versions you ship.

We should add test coverage for this.

Issue fork drupal_cms_site_template_base-3569396

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

phenaproxima created an issue. See original summary.

phenaproxima opened merge request !8

  • phenaproxima committed 2d429c88 on 1.x 
    feat: #3569396 Add test coverage for component usage

By: phenaproxima
phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented
Status: Active » Fixed

Merged into 1.x.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.