sorry, I'm a little confused here.. you have geolocation data in session store, but need it in default_scope?
can you just make a "fake" default_scope in the controller, where you do like @user = User.find(x).with_geo(lat: lat, long: long) and then basically return a user with a scope attached to that object, and use @user everywhere?
what might be some reasons that mail is being sent and received in our system, but 1 particular mail never reaches any inboxes despite the code giving no indication that it's failing to send?
I think in the case of including the relation directly on the main object, you have a lot more explaining in docs to do. When are there no related objects, when are they just not loaded, and which keys refer to relationships rather than just attributes
if you nest it under "relationships" all of that goes away. it's understood that if it's not there, it's not loaded. if it's there but empty, it's empty.
and the fact that it's under "relationships" makes it a related object, not an attribute
sure you can distinguish all of that by inspecting the JSON structure, which is easy for a person, but more difficult to read when you code it up
SteenJobs: that's my 2 cents on this. The more time I spend coding, the more I believe in the benefit of being explicit for everything.
SteenJobs: in the end, if everyone who is affected by this comes to the same understanding, I really don't think it matters. That's how specs are developed anyway, a group of people agreeing on something that makes sense to them.
I've got to run, but good luck and hope you come to a conclusion that you're happy with SteenJobs :)