Discussion
it's not uncommon to review patches and found adding `ActiveSupport::Concern` to a module, I guess are copy-paste?
> if we are not using anything related to `ActiveSupport::Concern` such as `included` or `class_method` blocks, then there's no need to be added since this would be a normal #ruby module
changing strategy about extra `ActiveSupport::Concern` inclusions, hope this helps 😊
> if we are not using features as `included`, `class_methods` blocks or autoloading modules, then let's remove it and keep it nice, lean, organic, all-natural, GMO-free #ruby module
@esparta GMO shaming is uncalled though.
@pointlessone yeah... didn't though about that, previously I had fat-free but it's also shammy.
The GMO is not against GMO itself, but companies who uses GMO as a greenwashing: they past 1 single certificate and make it seems like the whole company is conscious
@esparta Yeah. I suggest “all-natural” or "free range”. Or both in a case like this.
@esparta might be worth mentioning that `ActiveSupport::Concern` offers easier (automatic) handling of module dependencies (including a module inside another module).
A space for Bonfire maintainers and contributors to communicate
