Closed (won't fix)
Project:
Drupal core
Version:
main
Component:
contact.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
11 Nov 2025 at 10:53 UTC
Updated:
8 May 2026 at 12:52 UTC
Jump to comment: Most recent
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, etc. all have dependencies, which violates the basic rule of simple config
Comment #10
gábor hojtsyI agree with @berdir, there is no point in adding boilerplate for this now to tests. So won't fix then.