Open a separate issue to track hasManyThrough per request from @RaphaelDrai in
#2043 (comment)
Hello @bajtos,
It is important for us to have in LB4 the hasAndBelongsToMany (the direct many-to-many relation) that we are using in our LB3 application. We are actually in a transition process to move our LB3 application to LB4 and hasAndBelongsToMany is considered as an high priority.
May I suggest to have a new and separated case for the hasManyThrough in order to avoid confusion with this current case?
Open a separate issue to track
hasManyThroughper request from @RaphaelDrai in#2043 (comment)