Add negation of whenExtensionEnabled to Conditional Extender

davetodave178

The implementation of the Conditional Extender and particularly the whenExtensionEnabled function has been a great addition to the framework. I now stumbled across a case where a whenExtensionDisabled function would help to resolve an incompatibility issue.

I was wondering if others would also benefit from this?

luceos

davetodave178 usually when extensions are not compatible you would use the composer field conflicts. Is that what you are after or is this selectively doing something different?

davetodave178

luceos Yeah I'm actually leaning towards this (composer conflict) as well now in the case which prompted me to write this proposal FriendsOfFlarum/direct-links1

I guess there would still be use cases where compatibility can mostly be provided between two extensions, but for example, certain routes must not be added in the extension A, if extension B is enabled, for it to work. Perhaps this could be solved in another way, though?