This feels backwards, perhaps storage.js should have access to user-context and passing the user-id could be avoided.