AM
TradersVE
Everything can be solved with the factory.
Would you please post an example to the issue?
Size: a a a
2020 August 10
T
'yiisoft/form' => [
'fieldConfig' => [
'inputCssClass()' => ['form-control input field'],
'labelOptions()' => [['label' => '']],
'errorOptions()' => [['class' => 'has-text-left has-text-danger is-italic']],
'template()' => [your options]
],
],
'fieldConfig' => [
'inputCssClass()' => ['form-control input field'],
'labelOptions()' => [['label' => '']],
'errorOptions()' => [['class' => 'has-text-left has-text-danger is-italic']],
'template()' => [your options]
],
],
AP
T
You can do that with any widget.
AP
let me give you an example
AP
just a sec
T
If you need it just for one view?
AP
Or maybe it would work, I'll try it now.
AP
TradersVE
If you need it just for one view?
Is there any way to do it for just one view?
T
Yes
$fieldConfig = [
template() => "{label}\n<div class='input-group'>\n{input}\n<div class='input-group-append'><div class='input-group-text'><span class='fas fa-envelope fa-fw'></span></div></div>{hint}\n{error}</div>"
]
);
Field::widget([$fieldConfig])->config($form, 'email');
$fieldConfig = [
template() => "{label}\n<div class='input-group'>\n{input}\n<div class='input-group-append'><div class='input-group-text'><span class='fas fa-envelope fa-fw'></span></div></div>{hint}\n{error}</div>"
]
);
Field::widget([$fieldConfig])->config($form, 'email');
AP
TradersVE
Yes
$fieldConfig = [
template() => "{label}\n<div class='input-group'>\n{input}\n<div class='input-group-append'><div class='input-group-text'><span class='fas fa-envelope fa-fw'></span></div></div>{hint}\n{error}</div>"
]
);
Field::widget([$fieldConfig])->config($form, 'email');
$fieldConfig = [
template() => "{label}\n<div class='input-group'>\n{input}\n<div class='input-group-append'><div class='input-group-text'><span class='fas fa-envelope fa-fw'></span></div></div>{hint}\n{error}</div>"
]
);
Field::widget([$fieldConfig])->config($form, 'email');
Yep, but in that case I need to somehow also pass to the view all shared fieldconfigs
AP
that are set in provider or factory.
T
Arman Poghosyan
that are set in provider or factory.
No, widget has a factory, he will solve all the dependencies.
AP
Also, just some observation without trying: how am I supposed to do dynamic part in that case
T
for example you can pass the parameters through the controller and inject them into widget, it will work.
AP
An example: <div class='input-group'>\n{input}\n<div class='input-group-append'><div class='input-group-text'>{this part is dynamic}</div></div>
AP
that doesn't solve the part with dynamic thing. {dynamic part} is unique for each field in this case
AP
The idea is to allow specifying dynamic parts, and not changing the overall template in factory
AP
I think you misunderstood the issue