• ?

    user

    8 months ago
    Ahhh
  • ?

    user

    8 months ago
    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
  • r

    rp

    8 months ago
    @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.
  • ?

    user

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

    user

    8 months ago
    Is this intentional?
  • r

    rp

    8 months ago
    Ah. No. It should not be doing that. Thanks for pointing this out. Will fix
  • r

    rp

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

    rp

    8 months ago
    Will mostly likely release a fix for this today.
  • r

    rp

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

    user

    8 months ago
    Hello everyone 👋