You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There should exist an easy way to handover the data to the exporter:
$item->setNameValueWithoutUsergroup($string);
Don't mind my function name there. I know it is bad.
Why should this be implemented?
This reduces the overhead immense when you want to really fill in much attributes, variations, properties etc. might even be >80 lines of code in one function, which is not needed. The function may still do the same internally, but is way easier to call.
Why not refactoring yourself?
Refactoring myself would be also very impracticable, because either a create a function for each XML element, or I create a function where I also need to add the class Name as a parameter in order to do such calls, which results in a complete fiesta.
The text was updated successfully, but these errors were encountered:
Fixes#39.
Simples values, i.e. values other than properties, attributes, images
and usergroups, can now be set using a `Item::add<value>($value,
$usergroup = '')` method.
The corresponding `Item::set<value>(...)` methods still exist, so
compatibility is retained. However, this change should increment the
minor version number because functionality is added.
Simples values, i.e. values other than properties, attributes, images
and usergroups, can now be set using a `Item::add<value>($value,
$usergroup = '')` method.
The corresponding `Item::set<value>(...)` methods still exist, so
compatibility is retained. However, this change should increment the
minor version number because functionality is added.
Fixes#39.
At the moment I need three lines in order to set a name without a usergroup:
There should exist an easy way to handover the data to the exporter:
Don't mind my function name there. I know it is bad.
Why should this be implemented?
This reduces the overhead immense when you want to really fill in much attributes, variations, properties etc. might even be >80 lines of code in one function, which is not needed. The function may still do the same internally, but is way easier to call.
Why not refactoring yourself?
Refactoring myself would be also very impracticable, because either a create a function for each XML element, or I create a function where I also need to add the class Name as a parameter in order to do such calls, which results in a complete fiesta.
The text was updated successfully, but these errors were encountered: