I’m currently using it to store the current user from Absinthe request context, normal REST API requests, and inside phoenix channels. So that when resolving queries/mutations I don’t need to pass it down the flow. This allowed me to add logging (and other handling too) without changing function arities, and actually without modifying the existing code at all. I just now have the user everywhere, and it’s really cool.
dimamik
mudasobwa
Creator of Cure
This functionality has been extracted to NimbleOwnership v1.0.2 — Documentation a year ago or like. Basically, I believe NimbleOwnership somewhat covers the functionality of managing resources across processes.
2
