Problem/Motivation
When the standard install profile is used and Features is at its default configuration, the
core.entity_view_display.node.article.default
configuration item is assigned to the comment feature rather than the article one.
The problem appears to be that the base assignment plugin currently calls FeaturesManager::assignConfigDependents() after creating packages. In certain cases, this can lead to premature assignment.
core.entity_view_display.node.article.default
has core.entity_view_display.comment.comment.default among its required configuration entities.
Proposed resolution
Remove the call to $this->featuresManager->assignConfigDependents() from FeaturesAssignmentBaseType::assignPackages(). The need seems to be covered by the dependency assignment plugin.
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | features-assignment_base-2832261-4.patch | 1.32 KB | nedjo |
Comments
Comment #2
nedjoComment #4
nedjoOne of the test failures is from #2833258: Test failure from core change.
Attached patch updates the failing test. We no longer expect the
baseassignment plugin to handle dependencies.Comment #7
nedjo