Closed (fixed)
Project:
Upgrade Status
Version:
8.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Jan 2022 at 18:26 UTC
Updated:
16 Feb 2022 at 19:59 UTC
Jump to comment: Most recent
Comments
Comment #3
liam morlandComment #4
socialnicheguru commentedi do want modules that are disabled to be reported on
Comment #5
gábor hojtsyInteresting point that it could still be useful to report on obsolete/deprecated CONTRIBUTED extensions even if they are disabled, as this would underline the need to remove them and move on from them. (In case they were kept in the codebase for future use). However contributed projects could also include several extensions that may indepdendently be obsolete but you got them as a package, so you cannot / should not do much about them in that case either. Hm.
Comment #6
liam morlandAs I understand it, collectCoreDeprecatedAndObsoleteExtensions() only looks at core. So it would be a separate issue to change the handling of obsolete/deprecated contrib.
Comment #7
gábor hojtsyUh oh that is true :D The deprecation / obsolete marking system is to be used by contributed projects too, not sure why did I implement this only for core, but for core, definitely disabled extesions should not be reported on in this report. We should have a separate issue to general this to all extensions, but that will need to consider if a disabled sub-extension is part of a non-deprecation/not obsolete parent extension, and not report on it then. This fix should be good though and good find @Liam Morland.
Comment #9
gábor hojtsyCommitted this. Thanks again @Liam Morland!