Hey, I'm trying to add locale for /auth and useSWR dla translation. I use Next.js and ThirdPartyEmailPasswordReact. I don't know why url isn't url + locale (i18n) + /auth And I found https://github.com/supertokens/supertokens-auth-react/issues/233 but I don't know if I'll do the same what It's ok. Can someone helps me?

Right now we don’t have support for local languages 😦

So the description in the issue is all that’s possible. But that’s super hacky. But it would work

Finally, u could build your own UI for that form, whilst keeping other forms we provide in English.

But I've site with PL, EN and JP language.

I see. Then try out the component override method we describe in the issue above

But I don't know if I have to change to something more, because I use ThirdPartyEmailPasswordReact with social, not emailpassword.

And I don't know why /auth doesn't listen i18n 🤔

I would say that just change the /auth form and that’s it. Let the rest be in English if you can. Cause those r only reset password flow and Email verification flow.

You can even inject JS into the /auth route and change the language by finding the dom element. Might be easier

All have to be in 3 languages. I only have to get to the texts :/

I don't understand how do it

Hmm and if I use Only Session Management with Only Social login? But what can I apiDomain = apiWebsite and apiBasePath: '/api/auth', when I'll use SuperTokens Account? I have had forms done before

All you need to do to disable our UI is to pass a config value called disableDefaultImplementation in the forms you need to disable

And then build your own UI in there

I done it and even I have form on site. I have to delete SuperTokensComponentNoSSR component yet.

You may not want to remove that. Cause that makes sure that the page is loaded only if a session exists

Or maybe I’m misunderstanding which component you’re talking about

So I have to do how in link even if I use ThirdPartyEmailPassword and add where I have init in the config for the frontend social button (signInAndUpFeature: { providers: [ ThirdPartyEmailPasswordReact.Google.init(), ThirdPartyEmailPasswordReact.Facebook.init(), ThirdPartyEmailPasswordReact.Github.init(), ThirdPartyEmailPasswordReact.Apple.init(), ], }, )?

I mean in this file: https://supertokens.io/docs/thirdpartyemailpassword/nextjs/setting-up-frontend

Ah i see yea.. you can remove

<SuperTokensComponentNoSSR />

and build your own UI

Alternatively, you can disable only the sign in / up UI like shown in step 1 here: https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/embed-sign-in-up-form#step-1-disable-default-implementation

and build that on your own, whilst keeping the other UI the default one (in english). The other UI are: - reset password UI - email verification UI - social auth redirect UI (which is just a spinner and no text)

1:1 as in link, yes?

Not sure what you mean

I wrote "SuperTokens does not store custom form fields. You need to store them in your db post user sign up. " in https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/signup-form/adding-fields. Why aren't you do it? I need 2 fields yet for my project.

It’s something we plan on doing eventually.. it wasn’t a feature that was absolutely necessary to build

(Assume that you are using emailpassword recipe) in link. I'm using ThirdPartyEmailPassword

I see. When can it be?

I don't want to have 2 db.