Ahhh

Could the documentation include why the frontend client -> backend api -> supertoken managed service architecture was chosen instead of supertokens just being its own stand alone microservice like auth0 or firebase or w/e. Supertokens is more of a addon/extension of a api server than as stand alone api/microservice

@User yea you are right. It's architected differently. The reason for that is primarily easier customisability and secure sessions out of the box. We can add this to our docs. Thanks for the suggestion.

This is a little bizzare, this function sets Content-Type to text/html, and then proceeds to generate a json output...

Is this intentional?

Ah. No. It should not be doing that. Thanks for pointing this out. Will fix

@User have created an issue about this here: https://github.com/supertokens/supertokens-golang/issues/53

Will mostly likely release a fix for this today.

@User we have released a new version of the golang repo (v0.3.4) with the fix. Thanks for pointing it out.

Hello everyone 👋

hey @User !

what brings you here?

Ankur brought me here to join all of you cool people

got it! welcome :))

Hello everyone 👋 Ankit here, from India

Hey @Ankit Sharma

What brings you here?

Ankur invited me to join this group

Cool!! Happy to have you here. Let us know how we can help

Hello @User

Welcome & Hello Ambassadors. 🙌

Hello all, Vanshika here ! Thanks for the invite @User 🙌

Hi all, Puru here. Thanks to @User Tyagi for inviting me to the Ambassador program 🙇‍♂️

@User could you please ping @rp to get started with GitHub contributions

@User , there is a contributing channel here. You can post your message there.

I am trying to translate some parts of form but i find it hard to do so.I am trying to translate "or" divider and "continue with facebook" label.Is this possible with build in components?

You could run JS in a useEffect, find those elements using DOM functions and change the text

We don’t have translatable components yet. But will probably work on it soonish.. until then, the above recommendation is the best way.

Thanks for the solution

Are websockets supposed to work on a golang backend when wrapped with the supertokens verification wrapper?