Is there anything left todo? /cc @weaverryan

@wouterj I'll add an PHP-example along the Twig-example.

@weaverryan You mean passing tags instead of form? If so I think it would make sense when we show what the template might look like as you already suggested. I'll add that too.

I've added PHP examples and also a example prototype. But I still need to test those additions so even if it is mergable.

I really want this covered in the docs, and I know this approach works (though this PR still needs some tweaks - there are some comments posted that need to be dealt with). But, is this the best way? Is there no way to theme each "task" so that when you render the tasks (or render the prototype), they use the same markup? What we're doing here is basically not form theming, but instead using our own form rendering logic when outputting the prototype and the individual fields. I guess that's ok, but if we could just theme the field, I think it would be easier.

When customizing the rendering of a single field, the Form component uses entry as the segment name for collection entries. It does not allow to apply a separate theme for each element of the collection separately. Symfony 2.0 was doing it (using the collection index) and it was making the rendering slow while being unusable for customization in a real app.
So the following works:

{# assuming the root form is named "myform" and the collection field inside it is "tasks" #}
{% block _myform_tasks_entry_widget %}
<tr>
    <td>{{ form_widget(form.task) }}</td>
    <td>{{ form_widget(form.dueDate) }}</td>
</tr>
{% endblock %}

@stof So, using the block would make it more usable? If this is the case I'll test it and will update the cookbook-entry accordingly.

Ok, looks like I failed on rebasing. Anything I can do to fix this or would it be better to open a new PR?

your fail is that you rebase the symfony master branch on top of your branch instead of rebasing your branch. The way to fix this would be to rebase again, doing it with the right branch

@stof I basically followed the instructions from symfony.com. That is it, no?

@daFish Hm, do you think that you are able to solve the conflict? It's no problem if you can't do that. We can easily take your changes and rebase it for you. Just let us know what you think. :)

@xabbuh That would be great if you could that. However, I'd love to learn how to successfully rebase from master for the next time. ;)

@daFish are you sure you followed exactly the instructions in the doc ? To me, it looks like you ran the rebase command in your master branch instead of running it in your feature branch

@daFish Of course, I can do that tonight. Thank you for your nice contribution!

I'm pretty sure that the instructions in the documentation do actually work if you follow them step by step though.

@stof Yes, I am sure. That's what puzzles me as it wasn't the first time I did this.

@xabbuh Thank you.

Even with a rebase, this documentation is outdated, don't follow the right way of #1998 (comment) and so very little code stay valid.

https://github.com/daFish/symfony-docs/blame/ee3fc2983a220371204a9b28e25830b2a322f307/cookbook/form/form_collections.rst

@webda2l I know and this will be fixed when the rebase is done.

@daFish You can checkout the pr-1998-rebase. It is based on the 2.3 branch.

@daFish Do you have time to finish this?

@xabbuh Unfortunately I won't be able to finish this anytime soon. :(

@daFish thanks for noting that, we can take this over (no problem). Can you maybe provide a list of things you wanted to do? The only thing I see is rebasing, but I guess there are more things?

Thanks again for starting this!

@daFish Thanks for starting this. I opened #4629 to finish your great work. Do you recall what you intended to do beside rebasing on 2.3?