Is there any way to stop third-party settings pollution in Drupal 8?
- drupal 8 third party settings pollution fields
This is purely a site builder / developer experience issue.
The problem is that once a module that provides third-party settings to fields, like Display Suite or Custom Add Another, it adds an empty array to everywhere it could apply, before anything is configured there. It means these updates to the configuration add themselves whenever the configuration is touched for other reasons, so your diffs for configuration become very messy.
And it’s just ugly and seems completely unnecessary.
Why can’t the default state of anything that adds third party settings be nothing?
Here’s the issue where the concept of 3rd-party settings went in: Let 3rd party modules store extra configuration in EntityDisplay
It might provide some clues. @TODO review.
I’m thinking this might be fixable on the side of the modules that add their config? Or maybe a small tweak to core and guidelines for implementers would do it. I can’t imagine it’s intractable.
Examples of the configuration i want to dispense with:
- https://gitlab.com/find-it-program-locator/drutopia_findit_event/commit/22643b905f9f1c5dd4b28d782bdaf781c20c23a3
- https://gitlab.com/find-it-program-locator/drutopia_findit_place/commit/85a6639e46c67fd71c3c0b599f909bf7f4e250d5
- https://gitlab.com/find-it-program-locator/drutopia_findit_program/commit/a52e6f5bfc8633eb3cd4e731ac7305048f3fd468
- https://gitlab.com/find-it-program-locator/drutopia_findit_organization/commit/cad50c05ded3d4ed47a77ec570b4eb15cae2bd88
Oh! This seems promising at stopping the noise?
Do not add third-party setting if not used
@TODO follow up and maybe do the same for my CheckboxesJS module.