Create (or use) a Rubocop for the inverse keyword needed in the associations about rails-templates HOT 2 CLOSED

From my understanding, the existing cop is covering only the cases when the association is not a standard/default one, but 80% of our associations are standard ones (unless we use Rails engines, it's more around 60%). In either case, I think having a custom cop that requires the inverse_of explicit argument for ALL the associations might be preferable.

This answer assumes that the remaining 20% of work needed for the custom cop is not too hard of course, if there is any big blocker, we might want to consider (a).

from rails-templates.

@malparty I found an existing Rubocop rule that can achieve this. However, they seem more lax than our rule in Compass. This invalid example is considered valid according to their rule. It is because in this case, Rails can inferred the inverse_of.

So what should we do with this:
a) Use the existing Rails/InverseOf rule
b) If we prefer the explicit version, we can write a custom rule. The implementation is 80% finished (should've Google first 😅)

from rails-templates.