Thanks @Ron_Lavi for bringing this up,
With the current structure, there’s a lot of boilerplate, reducing it and simplify the process would be great; Creating multiple files just for a simple component (excluding a few different tests) is a total pain.
However, changing fundamental conventions and folder structure would impact the entire application, and I’m not sure if we have the capacity for this kind of refactoring. We can use a new convention set only on new code, but this might make the codebase even more confusing. Developers tend to copy & paste existing parts, and having different structures might create a mess.
How about creating a set of foreman dedicated eslint rules? if someone try to copy and reuse outdated code (like the connect HOC) eslint creates a warning.