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
Hi, I use nested multiplier in another multiplier, where both multipliers (inner and outer) have been set the copy number to 1 (default) and I found 2 bugs:
The nested (inner) multiplier has container containing inputs with some defaultValues set by BaseControl::setDefaultValue(). However, when I add a new copy by multiplier submit create button, the inputs of the new copy does not have its default values filled (only the first default copy does have)
When I add a new copy of the outer multiplier by its submit create button, the inner multiplier of the new outer multiplier copy does not have created its default copy (like the copy number being ignored), however the first default copy of the outer multiplier does have its outer multiplier with its default copy created
The text was updated successfully, but these errors were encountered:
Pressing “Create” inside a nested multiplier with fields with default values
did not work before 39725d3.
This has been reported in the first bullet point in
#56
The second bullet point is already covered by `testSendNested`
change introduced in the fix.
Hi, I use nested multiplier in another multiplier, where both multipliers (inner and outer) have been set the copy number to 1 (default) and I found 2 bugs:
The nested (inner) multiplier has container containing inputs with some defaultValues set by BaseControl::setDefaultValue(). However, when I add a new copy by multiplier submit create button, the inputs of the new copy does not have its default values filled (only the first default copy does have)
When I add a new copy of the outer multiplier by its submit create button, the inner multiplier of the new outer multiplier copy does not have created its default copy (like the copy number being ignored), however the first default copy of the outer multiplier does have its outer multiplier with its default copy created
The text was updated successfully, but these errors were encountered: