Follow-up to #2595543: Add "force" argument to FeaturesAssignerInterface::assignConfigPackages() →
Currently the 'excluded' constraint on features component packaging is skipped if the $force argument is passed to FeaturesManagerInterface::assignConfigPackage(. The original purpose of $force was to override the restriction that already-assigned configuration won't be reassigned.
However, there are cases including #2596007: Clear out stale excluded and required values → where we need finer granularity: the ability to skip constraints without invoking the forcing of reassigning of already-assigned configuration.
Add $skip_constraints argument to FeaturesAssignerInterface::assignConfigPackages() and related code as needed and pass to FeaturesManagerInterface::assignConfigPackage(). In 'profile' assignment plugin, skip required constraint if $skip_constraints == TRUE.
Active
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.