Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
#2938132: Ship layouts that make sense with Layout Builder's concept of sections added new layouts to Layout Builder, two of which have configuration.
There is no config schema defined for that configuration.
This should have been caught by tests, but was not
Proposed resolution
Add config schema
Fix the tests
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Comment | File | Size | Author |
---|---|---|---|
#15 | 3029061-schema-15-interdiff.txt | 4.9 KB | tim.plunkett |
#15 | 3029061-schema-15-PASS.patch | 4.58 KB | tim.plunkett |
#15 | 3029061-schema-15-FAIL.patch | 3.86 KB | tim.plunkett |
#2 | 3029061-schema-2-PASS.patch | 1.77 KB | tim.plunkett |
#2 | 3029061-schema-2-FAIL.patch | 1.05 KB | tim.plunkett |
Comments
Comment #2
tim.plunkettThere was existing test coverage of this plugin, but the configuration was never actually saved in config, only in tempstore.
Comment #4
xjmSo long as this is committed before 8.7.0-alpha1, it doesn't need an upgrade path or anything like that, since this change was just added in 8.7.x a couple weeks ago.
Comment #5
phenaproximaI'm not sure how I feel about the name of this data type. How about layout_plugin.layout_builder_multi_width?
Other than that, looks good and RTBC from me.
Comment #6
tim.plunkettTo me that implies it's owned by a module called
layout_plugin
. But honestly the name does not matter much to me, I just thought it would be better to not duplicate the info shared between the two plugins.Comment #7
phenaproximaOkay, fair enough. It's not really a big deal.
Comment #9
xjmCommitted and pushed to 8.7.x. Thanks!
Comment #10
tacituseu CreditAttribution: tacituseu commentedThis introduced random test failure in HEAD:
- https://www.drupal.org/pift-ci-job/1185181
- https://www.drupal.org/pift-ci-job/1185177
- https://www.drupal.org/pift-ci-job/1185180
Comment #11
alexpottI think this might have introduced a new fail on slower environments - see https://www.drupal.org/pift-ci-job/1185177 - both PHP 5.5 jobs have failed since this was committed.
Comment #13
alexpottUnfortunately this is back to needs work. I'm wondering why \Drupal\KernelTests\Config\DefaultConfigTest didn't catch this.
Comment #14
tim.plunkettBecause nothing in core ships with either of the two plugins configured.
I'll work on this tomorrow.
Comment #15
tim.plunkettSwitching from a functional test to a kernel test.
Comment #17
tim.plunkettAlso note that now we get the DefaultConfigTest failure in addition to the explicit fail, which is great.
Comment #18
phenaproximaOkay, well...cool!
Comment #19
xjmAdding 5.5 and 5.6 tests to be safe.
The 5.6 test has been segfaulting for weeks now and that was not introduced by this patch.
Comment #21
xjmCommitted and pushed to 8.7.x. Thanks for catching the test regression!