Thanks for the feedback! For items number 3 and 4 I was hoping to find a simple "users" table in the schema so that I could easily track it in hasura : hasura.io/docs/latest/graphql/core.... Instead, supertokens provided a more complicated schema that would have taken a significant time investment to understand and manage. This is likely due to the nature of building an auth service so not a bad thing.
The nHost team does provide an open source auth solution that has a nice clean schema that works out of the box with Hasura : github.com/nhost/hasura-auth
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the feedback! For items number 3 and 4 I was hoping to find a simple "users" table in the schema so that I could easily track it in hasura : hasura.io/docs/latest/graphql/core.... Instead, supertokens provided a more complicated schema that would have taken a significant time investment to understand and manage. This is likely due to the nature of building an auth service so not a bad thing.
The nHost team does provide an open source auth solution that has a nice clean schema that works out of the box with Hasura :
github.com/nhost/hasura-auth