Thank’s for answer. Didn’t saw that notice. Are you planning to make inverseOf for relations involving a junction table? If not, what’s reason for not making it?
I’m not a developer of the framework, so the following is only a humble opinion of mine.
IMO, "inverseOf" has a very limited range of use cases.
It may be useful for "hasMany" relation where the inverse of it is just one model instance. But the inverse of "hasOne", which can be many instances, is not very easy to use.
Please read the description of the API for the detail:
A has_many relation via junction table can be divided to a pair of has_many and has_one relations.
For example, a TemplateType has many TemplateTypeToSites and a TemplateTypeToSite has one Site.
Since you can define "inverseOf"s for those 2 simple relations, you would be able to make use of the "inverseOf" feature using this pair of the relations.
But I’m afraid it’s not very easy to use nor very useful.