Problem/Motivation
#2971699: Content Moderation and Workspace don't work together had the use case to prevent a module from being installed if another one is also installed. It achieved that goal with two separate hook_requirements() implementations, which is a bit clunky.
Proposed resolution
Allow modules to declare their incompatibilities with a conflicts section in their .info.yml file.
Remaining tasks
Discuss, agree, write a patch, etc.
User interface changes
Nope.
API changes
API addition: modules will be able to declare their incompatible states more easily.
Data model changes
Nope.
Comments
Comment #2
amateescu commentedI started looking into this a bit for #2971699: Content Moderation and Workspace don't work together, but it's a lot to take in for someone unfamiliar with this code so I'm not sure I can do it myself before 8.6.0-alpha1.
Here's my WIP patch which builds a list of conflicts based on a new
conflictskey that modules could use in theirinfo.ymlfile.Comment #5
pandaski commentedThis is a duplicate of #92233
Comment #6
amateescu commented@Joseph Zhao, thanks for finding those. Marking as a duplicate of #746752: New "conflicts" property for .info.yml extension files.