None of the \Magento\Framework\App\Config\ValueInterface methods are used by the core outside of the particular implementation \Magento\Framework\App\Config\Value
|
|
0
|
952
|
January 11, 2016
|
How to create a translatable custom model?
|
|
0
|
683
|
April 12, 2017
|
How to implement a one-to-many relationship between a custom entity and products?
|
|
1
|
2640
|
April 7, 2017
|
A backend model should always be a \Magento\Framework\Model\AbstractModel
|
|
3
|
2054
|
January 24, 2016
|
\Magento\Framework\App\Config\Value::afterLoad() method breaks specification of the overriden parent method \Magento\Framework\Model\AbstractModel::afterLoad() by not calling it, ignoring its logic, and having a different result type
|
|
1
|
1715
|
January 11, 2016
|
How does Magento 2 save a backend config form vield value?
|
|
1
|
5326
|
December 6, 2015
|
Logical error: Magento 2 checks whether a backend config form field's «backend_model» implements the \Magento\Framework\App\Config\ValueInterface interface only, but actually calls the «backend_model» for much more methods (absent in the interface)
|
|
1
|
2022
|
January 11, 2016
|
The methods \Magento\Framework\App\Config\ValueInterface::getFieldsetDataValue() and \Magento\Framework\App\Config\Value::getFieldsetDataValue() are declared but never used
|
|
1
|
1487
|
January 11, 2016
|
The method \Magento\Framework\App\Config\ValueInterface::isValueChanged() should be removed from the interface because it is used only internally by a particular interface implementation: \Magento\Framework\App\Config\Value
|
|
1
|
1259
|
January 11, 2016
|
The method \Magento\Framework\App\Config\ValueInterface::getOldValue() should be removed from the interface because it is used only internally by a particular interface implementation: \Magento\Framework\App\Config\Value
|
|
1
|
1173
|
January 11, 2016
|
What is the «backend_model» for a backend configuration's form field?
|
|
1
|
3507
|
November 17, 2015
|