I’m happy to provide some real code from our app if that helps?
What I don’t understand is why there needs to be a way to reload has_many but not a way to reload has_one.
In our apps most has_ones are related to a has_many, for example picking the “active” one.
We need to reload the has_many when something may have changed the list. We need to find the new “active” one in the same situation.
Totally fine with any API but to argue that has_many has needs that has_one does not share seems very strange.
Do you see where I’m coming from?