Feature request

I've just finished talking with @coder2000 about this. They were trying to render a collection, rendering different components based on another argument. So their aim was for User::Component to render a collection of User::Actives, for example. It's got me thinking about how collections would work with dynamically chosen components — that seemed to be their original aim as they've mentioned in a discussion. There's been some talk about rendering the same component with different templates in the past, which I've done some work to try and establish patterns for, but this was a nice reminder that it still sort of needs to be thought about for collections.

Let's say you're rendering a list of user profiles, some of which you'd like to show in less detail because they're incomplete, not visible, or otherwise. One way you could do that is to render FullProfileComponents, and render NullProfileComponents for those that aren't present. I think it would follow that you should be able to create a 'factory component' like this:

class ProfileComponent < ApplicationComponent
  with_collection_parameter :profile

  def self.new(profile:)
    (profile.complete? ? FullProfileComponent : NullProfileComponent).new(profile: profile)
  end
end

<%= render ProfileComponent.with_collection(@profiles) # renders `Full` and `NullProfileComponent` on a case-by-case basis %>

The only thing stopping this at present is validate_collection_parameter, which should check .new's parameters as well as #initialize. I wanted to open up discussion before making any changes - what do folks think about this as a pattern?