Needs work
Project:
Drupal core
Version:
main
Component:
contact.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
11 Nov 2025 at 10:53 UTC
Updated:
4 Feb 2026 at 23:25 UTC
Jump to comment: Most recent
Contact module is being deprecated. Usages is tests not in Contact needs to removed and test coverage moved to the Contact module.
contact.settings is used in \Drupal\Core\Config\Schema\SchemaCheckTrait. Can this just be removed? See related issue #3425992: contact.settings, filter.settings, search.settings etc. all have dependencies, which violates the basic rule of simple config
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
berdirI'm not sure if this can just be removed. It would need to be duplicated into all contact tests that trigger this, which could be a lot. Including contrib tests such as contact_storage which would then break without this as well. I guess it will need to happen eventually as they are moved out of core. Start by removing it and seeing which tests break I suppose. Then add it back in setup() of those specific tests.
Comment #4
quietone commentedComment #5
quietone commentedComment #6
berdirThis is worse than I thought because it also affects Tests that enable all modules of course.
We'd need a trait that unifies skipping some modules and update them all .
But I wouldn't bother. Not now. This is not a blocker, it will not fail if contact is removed, it is an exclude list.
And I think I disagree with how it was done in the first place. We imho shouldn't trigger errors for something that can't be fixed.
Comment #9
andypostAs I see it does not affect deprecation so could be close in favour of existing TODO #3425992: contact.settings, filter.settings, search.settings etc. all have dependencies, which violates the basic rule of simple config