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
Extending blocks is a fairly common thing to do in contrib. block_class for example, that allows to assign custom classes to blocks that can then be used for theming.
Right now, they have to store their settings separately, making it hard to deploy.
Proposed resolution
Integrate with the third party settings API
Remaining tasks
User interface changes
API changes
New methods on BlockInterface. (config entity block, not the block plugins)
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | block-third-party-2358677-6-interdiff.txt | 505 bytes | Berdir |
| #6 | block-third-party-2358677-6.patch | 2.4 KB | Berdir |
| #4 | block-third-party-2358677-4.patch | 1.9 KB | Berdir |
| #1 | block-third-party-2358677-1.patch | 1.91 KB | Berdir |
Comments
Comment #1
BerdirFirst patch.
Comment #3
swentel CreditAttribution: swentel commentedRelated, #2361775: Third party settings dependencies cause config entity deletion
Comment #4
BerdirReroll.
Given the situation with the config schema in that issue, I don't know how to continue there, so giving this another push. Would be great for block_class: #2198023: Port Block Class to Drupal 8
Comment #6
BerdirFixed the test. Wondering if we really need test coverage for every third party settings implementations we add. On the other side, we often find bugs when actually providing an example implementation ;)
Comment #7
Berdir#2361775: Third party settings dependencies cause config entity deletion happened, awesome.