-
Notifications
You must be signed in to change notification settings - Fork 98
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
Docs misunderstanding #81
Labels
Comments
I agree most of the time the 3rd line would be used only on the client. However the repo can be called from the server also. |
Need clarify it in doc.
20 дек. 2017 г. 13:59 пользователь "Eddyystop" <notifications@github.com>
написал:
… I agree most of the time the 3rd line would be used only on the client.
However the repo can be called from the server also.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#81 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAwPIyRx9iwidghN9mf6MRuE7yDum5Qfks5tCQS7gaJpZM4RILzD>
.
|
Yeah, confusing. |
Done. Please make any additional comments in authentication-local-management. Full details on the authentication-local-management rewrite at in https://github.com/feathers-plus/authentication-local-management/blob/master/misc/upgrading.md |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Client configuration say:
but looks like 2 first lines is server configuration. for client only last required. more one, first 2 lines makes it not works at all
The text was updated successfully, but these errors were encountered: