• repomaa

    repomaa

    1 year ago
    alright
  • r

    rp

    1 year ago
    userData could contain roles or what not. Should be enough to do authorization based on the payload Yes
  • repomaa

    repomaa

    1 year ago
    i think i'll give it a try when i get the chance
  • r

    rp

    1 year ago
    cool! lmk if it works..
  • repomaa

    repomaa

    1 year ago
    will do
  • ?

    user

    1 year ago
    It would be a lot better if the SuperTokens UI was framework agnostic. E.g if it was made using Stencil Web Components, this means it'd be plug and play for almost every framework. And then if the core functionality of recipes from the React library was extracted so it could be extended with custom http clients etc. I'm trying to extract it as an Angular library, which means I have to rewrite both
    supertokens-website
    and
    supertokens-auth-react
  • c

    codefingers

    1 year ago
    Yes, thought so too... I feel it was designed this way to ensure specific issues surrounding session management around those frameworks are properly dealt with... A similar architecture you see with IaaS like Firebase
  • r

    rp

    1 year ago
    We specifically built our frontend for React, using react components since it allows us to provide a UI without the need for iframes, and to enable maximum customisation to users of reactJS.
  • c

    codefingers

    1 year ago
    Always easier to satisfy and grow around a small niche
  • r

    rp

    1 year ago
    i don't think react is a small niche though..