Collection field components with block support

[rowofpixels]

trafficstars

I saw this comment in a past PR: https://github.com/pantographe/view_component-form/pull/29#issuecomment-876579518 about adding collections without the block support first. I read through a number of issues in https://github.com/github/view_component related to form fields and it seems like it's not a simple problem to solve.

I'm curious whether there is a plan to support these fields when used with a block like so:

<%= f.collection_check_boxes :ids, MyModel.all, :id, :name do |b| %>
  <%= b.check_box %>
  <%= b.label %>
<% end %>

Right now the issue is that b is the component object rather than a builder object. I'm not sure what the right approach would be in a view component form builder.

[nicolas-brousse]

We did something similar for LabelComponent but we missed it on collections.

For LabelComponent we did this: https://github.com/pantographe/view_component-form/blob/2803648f9e7c8317f2322bdffe6608b7ebbb3777/app/components/view_component/form/label_component.rb#L31-L39 https://github.com/pantographe/view_component-form/blob/d38c459dfa21ded2bb0f8dffffadcd0d00644850/spec/view_component/form/label_component_spec.rb#L45-L72

[wooly]

We've just come up against this today and it would be super useful to have. I started poking around to see if I could thread things through, but I can't quite wrap my head around it as in the collection checkbox case there's a new builder instantiated for each item in the collection here: https://github.com/rails/rails/blob/83217025a171593547d1268651b446d3533e2019/actionview/lib/action_view/helpers/tags/collection_helpers.rb#L89 which I'm guessing would need to be yielded somehow. Will try to workaround it for now.

[Spone]

@wooly I don't know if you're aware of the new compatibility module available in ViewComponent, to fix problems with blocks that we had in the past: https://github.com/ViewComponent/view_component/pull/1650

Let us know if you figure out a workaround, it will be useful to fix this issue. And feel free to open a PR if you have time!

[wooly]

I managed to get it working, but not in a super-idiomatic way. I've pushed up an example PR here: https://github.com/pantographe/view_component-form/pull/142

The idea is to pass an additional proc option to use as the block for the render call, then strip that out of the options prior to render so the component can be initialized with the options-less-proc hash, then pass the proc as the block to render.

[wooly]

@nicolas-brousse any feedback on that PR to validate that it's the right approach?

[nicolas-brousse]

Hi @wooly, Thank you for your interest in this. I'll try to found a bit of time this week or the next one to have a look on this.

[wooly]

Thanks! I’m happy to knock it into shape with any feedback and flesh out some specs too.

[Spone]

@wooly :wave: we reviewed your PR. We spent some time trying to find a way closer to Rails' syntax, but it seems to be quite a difficult task. For now, let's go with your suggestion!

[coder2000]

I found a need for this solution in my application and I used code similar to #148 for my radio buttons. ~~I didn't need to change my view at all and it works just the same. Only issue I have found is the text fields while I call titleize on them in my view appear as all lower case letters.~~

I was wrong. The code I was using was essentially the default collection with no block rendering. I think the issue is calling the components in the block properly because I get parameter errors.