Rudie Dirkx

If I `dd($taco_test);` before adding it to the parent form, I can see all checkboxes' names: #name: "professions[]" ~~That `[]` comes from `buildCheckableChildren()` and I think it's correct, so it...

Temporary local 'fix': ``` public function buildForm() { // ... $this->fixChildFormCheckboxes($this->taco_test->professions); } protected function fixChildFormCheckboxes(FormField $field) { foreach ($field->getChildren() as $child) { $child->setName($field->getName()); } } ``` because `form.taco_test.professions`'s name is...

Still broken, but too complex for me. Work-around: explicit `setName()` after every plain form creation: $career_choice_test = $this->formBuilder->plain()->setName('career_choice_test'); and in a subform: 'class' => $this->formBuilder->plain()->setName("career_choice_test[$name]")

All options are (or should be) on https://kristijanhusak.github.io/laravel-form-builder/field/collection.html There are no `allow_add` and `allow_remove`. During validation, collection elements are collected dynamically. If you send 6, 6 will be validated. No...

After validation (without redirecting), you could print these for clarity: print_r($form->getAllAttributes()); print_r($form->getFieldValues()); Which values it accepts, depends on how you feed original data into the form.

@AdamKyle It only does this if `!Arr::get($model, $dotName)`. Not always. How did you build your form, and what's its input?

I'm still curious. How did you build your form, and what's its input?

And how is your form named or not named? And why? Usually only child forms are named. Named forms expect the model to be in the name in the model....

Most of this doesn't do anything. What does `join` vs `implode` do? Are you just copying your IDE's improvements?

The `choice` type is broken is several ways. All `ParentType` fields are somewhat broken. I'm starting v2 without it.