lynndylanhurley / devise_token_auth

Token based authentication for Rails JSON APIs. Designed to work with jToker and ng-token-auth.
Do What The F*ck You Want To Public License
3.54k stars 1.13k forks source link

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

Open charlypoly opened 3 years ago

charlypoly commented 3 years ago

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!

lynndylanhurley commented 3 years ago

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.

charlypoly commented 3 years ago

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 commented 3 years ago

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

EvitanRelta commented 2 years ago

@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: "whyisthisnotworking@email.com",
    password: "123456"
});
await client.get("/tasks");     // doesn't set any auth headers