Consider renaming container.AutoGroupType

[aaronc]

This seems unintuitive. container.OnePerModuleType is clearer. Maybe container.AutoGroupType can become container.ManyPerContainerType or something?

[facundomedica]

While I was studying the container package I saw this issue :) (nothing fancy, just a quick replace and tests still run)

[aaronc]

Does this seem like an improvement to you? Is it easier to under?

[facundomedica]

Yes, my thought is that AutoGroup describes "what happens to it" while ManyPerContainer describes "what you can do with it" which IMO is what you want to know when you are implementing it; so you don't really care how it's being handled internally.
That being said, I'm still wrapping my head around the container package and how to implement it, so I might be very wrong ☝️

[aaronc]

What about simply ManyType?

[facundomedica]

I gave this some thought and I think ManyPerContainer works better, at least it's more consistent with OnePerModule; just Many sounds too broad. If you agree feel free to merge the PR, I was holding back that until we come to a conclusion

[aaronc]

Sounds good let's merge