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.When running functional tests with features enabled we receive the following errors:
Drupal\Core\Config\Schema\SchemaIncompleteException: Schema errors for features.bundle.default with the following errors: features.bundle.default:assignments.alter.core missing schema, features.bundle.default:assignments.alter.uuid missing schema, features.bundle.default:assignments.alter.user_permissions missing schema
The module also fails when usinng the config inspector module. Screen shot of config inspector output is attached.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | features-config_schema-2858909-7.patch | 3.43 KB | Grimreaper |
| |||
| #2 | 2858909.patch | 534 bytes | dsjordan |
| |||
| Screen Shot 2017-03-08 at 1.37.00 PM.png | 89.63 KB | dsjordan | |
Comments
Comment #2
dsjordan CreditAttribution: dsjordan as a volunteer commentedpotential patch file attached
Comment #3
dsjordan CreditAttribution: dsjordan as a volunteer commentedComment #4
nedjoLooks good to me.
Comment #5
mpotter CreditAttribution: mpotter at Phase2 commentedSo wait, this doesn't make sense to me.
Where is the "assignment.alter" coming from? That isn't a plugin provided by Features. It is something else? The UUid for config is added by core when config is exported to the sync directory. Features strips that out. I don't see any config schemas in core adding those keys, so I don't understand why Features would need to add them to our schema.
I think this needs more investigation.
@Nedjo: am I missing something since you said this looks good?
Comment #6
nedjo@mpotter: these are coming from the 'alter' features assignment plugin I added in #2599278: Move export processing to a configurable plugin. That plugin adds configuration settings 'uuid', 'core', and 'user_permissions', but I neglected to update the features bundle schema accordingly.
But looking again at the patch, we shouldn't be adding these properties directly to
features.assignment.*. Instead, we need a new section forfeatures.assignment.alter.Comment #7
GrimreaperHello,
I made a patch before seing that this issue exists.
It declares the config type "features.assignment.settings" so it can be used to refactor existing assignment config and easily declare the alter assignment.
Thanks for the review.
Comment #8
juampynr CreditAttribution: juampynr at Lullabot commentedPatch applies cleanly and fixes the issue. I am now able to run JavaScript tests without getting this error. The tests use a module that has exported settings via Features.
Comment #10
mpotter CreditAttribution: mpotter at Phase2 commentedCommitted to 35f1cd8. The addition of features.assignment.settings to remove all the dup code is great, thanks!
Comment #11
GrimreaperThanks for the commit :)