Why does findOrCreateUser promise to return a user object?

Question

The findOrCreateUser function expects a user object returned. Why is this? What does it do with it?

Does it merely read and store the user's id for later reference?

Also, why doesn't it have a callback? Otherwise isn't it going to block whilst the code goes to the database?

Some insight.... https://github.com/bnoguchi/everyauth/issues/116 — Ian Warburton, Oct 22 '14 at 16:19

score 0 · Answer 1 · answered Oct 21 '14 at 22:51

0

My guess is findOrCreateUser is pseudo-code, so you can define your own method to be chained in everyauth's process.

answered Oct 21 '14 at 22:51

Julian H. Lam

Sure... chain it in but why does it want me to return a user object? – Ian Warburton Oct 22 '14 at 14:00

1 Answers1