Like this thread said: Override abstract class in Magento 2 in Magento 1,
I can just create a fully new class. In Magento 2, we need to use plugins, but plugins only allow me to modify existing methods. What do I have to do if I want to add a new method?
Example:
This class vendor/magento/module-ui/Component/AbstractComponent.php, has an array of components: $components, there is no function to unset/delete elements for that array. So how can I create that function?
overloading a class in M1 in the autoloader via community or local directory (like suggested in the question you linked) was considered bad practice in M1 for very good reasons.
Mostly you lose the ability to upgrade your Magento instance if the original class is changed in places, you did not consider in your overloaded class.
Actually, I cannot think of any use case, where you really need to add methods to an abstract class, since you always can add your own logic to an own class and integrate it in a plugin/observer/ViewModel/XML config
The best way would be, introduce a new class that extends the abstract class for your specific use case and then use your class where needed.
If you need to remove elements from a Ui Component, there is also likely a better way to do it via layout / a plugin on the layout processor / changing the js file that requires it.
So if you describe your specific use case there might be a better answer to this.
I don't see how you can do that without completely overriding the class. In the case of your example, you can disable individual components by setting the "disabled" item to the "data" argument in the XML. For instance:
<?xml version="1.0" encoding="UTF-8"?>
<form xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Ui:etc/ui_configuration.xsd">
<fieldset name="general">
<field name="title">
<argument name="data" xsi:type="array">
<item name="disabled" xsi:type="boolean">true</item>
</argument>
</field>
</fieldset>
</form>
This effectively removes 'title' from the $components array.
This is due to the createChildComponent method in the Magento\Framework\View\Element\UiComponentFactory class:
protected function createChildComponent(
array $bundleComponents,
ContextInterface $renderContext,
$identifier
) {
list($className, $arguments) = $this->argumentsResolver($identifier, $bundleComponents);
if (isset($arguments['data']['disabled']) && (int)$arguments['data']['disabled']) {
return null;
}
$components = [];
foreach ($bundleComponents['children'] as $childrenIdentifier => $childrenData) {
$children = $this->createChildComponent(
$childrenData,
$renderContext,
$childrenIdentifier
);
$components[$childrenIdentifier] = $children;
}
$components = array_filter($components);
$arguments['components'] = $components;
if (!isset($arguments['context'])) {
$arguments['context'] = $renderContext;
}
return $this->objectManager->create($className, $arguments);
}
You can create a new class and extend the magento/module-ui/Component/AbstractComponent class
use Magento\Ui\Component\AbstractComponent;
class YourNewClass extends AbstractComponent
{
...
How about writing a plugin on the getChildComponents function and putting your logic? It is not something we'd want to do of course, but it does seem the closest match to take over the property component in this abstract class.
You can use class preference ,using before, around and after in the required method . Please check the docs for further details http://devdocs.magento.com/guides/v2.1/extension-dev-guide/plugins.html
You have not found the correct Component class. The abstract class cannot be overridden and cannot add methods. The abstract class must have inherited classes. Find the class with the current function and rewrite it.
