devise_token_auth icon indicating copy to clipboard operation
devise_token_auth copied to clipboard

Is devise-token-auth-client npm package meant to be public?

Open charlypoly opened this issue 4 years ago • 4 comments

Hi @lynndylanhurley 👋🏼

Sorry to land this question here, but is it part of the devise_token_auth project and I didn't know how to contact you about the devise-token-auth-client npm package.

While working on a project that I migrate from Angular (using ng-token-auth) to React, I discovered your new implementation devise-token-auth-client available on NPM. However, the repository linked to this package seems to be private - or deleted, under the graveflex organization.

I was wondering if this project is meant to be public on NPM, and if so, do you plan to make the source open?

Thank you for your understanding!

charlypoly avatar Jun 01 '21 15:06 charlypoly

Hey, yes I've been meaning to open source that for awhile now, but I keep getting distracted while writing the documentation. Would you like access to the repo so that you can help me test?

On Jun 1, 2021, at 10:48 AM, Charly POLY @.***> wrote:

Hi @lynndylanhurley https://github.com/lynndylanhurley 👋🏼

Sorry to land this question here, but is it part of the devise_token_auth project and I didn't know how to contact you about the devise-token-auth-client npm package.

While working on a project that I migrate from Angular (using ng-token-auth) to React, I discovered your new implementation devise-token-auth-client available on NPM. However, the repository linked to this package seems to be private - or deleted, under the graveflex organization.

I was wondering if this project is meant to be public on NPM, and if so, do you plan to make the source open?

Thank you for your understanding!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/lynndylanhurley/devise_token_auth/issues/1489, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADSIROORKOAHE2TSIQPLODTQT6LDANCNFSM4546L2XA.

lynndylanhurley avatar Jun 01 '21 15:06 lynndylanhurley

Yeah, I would love to give it a try and give feedback!

Thank you!

On Tue 1 Jun 2021 at 6:00 PM, Lynn Dylan Hurley @.***> wrote:

Hey, yes I've been meaning to open source that for awhile now, but I keep getting distracted while writing the documentation. Would you like access to the repo so that you can help me test?

On Jun 1, 2021, at 10:48 AM, Charly POLY @.***> wrote:

Hi @lynndylanhurley https://github.com/lynndylanhurley 👋🏼

Sorry to land this question here, but is it part of the devise_token_auth project and I didn't know how to contact you about the devise-token-auth-client npm package.

While working on a project that I migrate from Angular (using ng-token-auth) to React, I discovered your new implementation devise-token-auth-client available on NPM. However, the repository linked to this package seems to be private - or deleted, under the graveflex organization.

I was wondering if this project is meant to be public on NPM, and if so, do you plan to make the source open?

Thank you for your understanding!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/lynndylanhurley/devise_token_auth/issues/1489>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AADSIROORKOAHE2TSIQPLODTQT6LDANCNFSM4546L2XA .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lynndylanhurley/devise_token_auth/issues/1489#issuecomment-852242659, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJRVYXCHZWGSKY7JZ6PQLLTQT7ZDANCNFSM4546L2XA .

--


Charly POLY https://charlypoly.com

charlypoly avatar Jun 01 '21 17:06 charlypoly

@lynndylanhurley I'm still in for testing it! 🙂

charlypoly avatar Jun 02 '21 15:06 charlypoly

@lynndylanhurley Yoo, may I know how to use the devise-token-auth-client package?

I assumed I just needed to do client.emailSignIn, then I can use client as an axios instance and do client.get("/my_data") to get my data.

But it seems like the client doesn't automatically set the auth headers (eg. access-token) in the subsequent get requests after signing in.

My code:

const client = new ApiClient ({
    baseURL: 'http://localhost:3000/api'
});
await client.isInitialized;
await client.emailSignIn({
    email: "[email protected]",
    password: "123456"
});
await client.get("/tasks");     // doesn't set any auth headers

EvitanRelta avatar Jan 10 '22 06:01 EvitanRelta