MAGETWO-71257: Need to disable module output by configuration

Author: Eric Bohanon

app/code/Magento/Config/Block/System/Config/Form/Fieldset/Modules/DisableOutput.php

@@ -21,41 +21,25 @@ class DisableOutput extends \Magento\Config\Block\System\Config\Form\Fieldset
 {
     /**
      * @var \Magento\Framework\DataObject
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      */
     protected $_dummyElement;
 
     /**
      * @var \Magento\Config\Block\System\Config\Form\Field
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      */
     protected $_fieldRenderer;
 
     /**
      * @var array
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      */
     protected $_values;
 
     /**
      * @var \Magento\Framework\Module\ModuleListInterface
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      */
     protected $_moduleList;
 
@@ -112,11 +96,7 @@ public function render(\Magento\Framework\Data\Form\Element\AbstractElement $ele
     }
 
     /**
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      * @return \Magento\Framework\DataObject
      */
     protected function _getDummyElement()
@@ -128,11 +108,7 @@ protected function _getDummyElement()
     }
 
     /**
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      * @return \Magento\Config\Block\System\Config\Form\Field
      */
     protected function _getFieldRenderer()
@@ -146,11 +122,7 @@ protected function _getFieldRenderer()
     }
 
     /**
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      * @return array
      */
     protected function _getValues()
@@ -167,11 +139,7 @@ protected function _getValues()
     /**
      * @param \Magento\Framework\Data\Form\Element\Fieldset $fieldset
      * @param string $moduleName
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      * @return mixed
      */
     protected function _getFieldHtml($fieldset, $moduleName)

lib/internal/Magento/Framework/Module/Manager.php

@@ -21,11 +21,7 @@ class Manager
 {
     /**
      * @var Output\ConfigInterface
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      */
     private $outputConfig;
 
@@ -36,11 +32,7 @@ class Manager
 
     /**
      * @var array
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      */
     private $outputConfigPaths;
 
@@ -93,11 +85,7 @@ public function isOutputEnabled($moduleName)
      *
      * @param string $moduleName Fully-qualified module name
      * @return boolean
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      */
     protected function _isCustomOutputConfigEnabled($moduleName)
     {

lib/internal/Magento/Framework/Module/Output/Config.php

@@ -18,31 +18,19 @@ class Config implements \Magento\Framework\Module\Output\ConfigInterface
 {
     /**
      * XPath in the configuration where module statuses are stored
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      */
     const XML_PATH_MODULE_OUTPUT_STATUS = 'advanced/modules_disable_output/%s';
 
     /**
      * @var \Magento\Framework\App\Config\ScopeConfigInterface
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      */
     protected $_scopeConfig;
 
     /**
      * @var string
-     * @deprecated 100.2.0 Magento does not support disabling/enabling modules output from the Admin Panel since 2.2.0
-     * version. Module output can still be enabled/disabled in configuration files. However, this functionality should
-     * not be used in future development. Module design should explicitly state dependencies to avoid requiring output
-     * disabling. This functionality will temporarily be kept in Magento core, as there are unresolved modularity
-     * issues that will be addressed in future releases.
+     * @deprecated 100.2.0
      */
     protected $_storeType;