Skip to content
This repository has been archived by the owner on Apr 23, 2019. It is now read-only.

Note that auth must be configured after rest/socket clients #36

Merged
merged 1 commit into from
Apr 3, 2017

Conversation

hubgit
Copy link
Contributor

@hubgit hubgit commented Apr 3, 2017

It would be useful to note in the documentation that the auth client must be configured after the rest client. If they're configured in the opposite order, the auth token doesn't get added to the request header.

It would be useful to note in the documentation that the `auth` client must be configured _after_ the rest client. If they're configured in the opposite order, the auth token doesn't get added to the request.
@marshallswain
Copy link
Member

Oh, good addition. Would you mind updating wherever applicable in the new API docs? https://github.com/feathersjs/feathers-docs/blob/auk/api/authentication/client.md

@marshallswain marshallswain merged commit 5e657aa into feathersjs-ecosystem:master Apr 3, 2017
hubgit added a commit to hubgit/feathers-docs that referenced this pull request Apr 3, 2017
As requested in feathersjs-ecosystem/authentication-client#36 (comment)

I haven't added a note to the main Configuration section as it only shows one line there.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants