Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reason for /connect/... routes #39

Open
WORMSS opened this issue Oct 14, 2016 · 0 comments
Open

Reason for /connect/... routes #39

WORMSS opened this issue Oct 14, 2016 · 0 comments

Comments

@WORMSS
Copy link

WORMSS commented Oct 14, 2016

I am sorry, I really do not understand the reason for the /connect/.../ routes in this example?

/auth/google and /connect/google seem to be identical? And the intelligence of linking the accounts are all done in the Strategy..

I am sorry if I am missing what could be an obvious point.

The only thing I can think of is if you wanted /connect/google/ and /auth/google to render different pages and this example just hasn't gone that complex?
If that is the case then it wasn't obvious to me that that was the case.

  • Colin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant