You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we must call this an auth package, I don't see a reason why only one type of database should be used(which currently is mongodb). A developer should be able to choose a database which matches with the database he/she wishes to use throughout the development circle of their project and not compelling them to use only a specific kind of database. They should be able to choose to use either Mongodb, Postgres, Mariadb, Redis and so on for as many databases we have on the package.
A Mysql database server should be set up and integrated to the sign-up and sign-in functions along side the jwt-token function.
The text was updated successfully, but these errors were encountered:
If we must call this an auth package, I don't see a reason why only one type of database should be used(which currently is mongodb). A developer should be able to choose a database which matches with the database he/she wishes to use throughout the development circle of their project and not compelling them to use only a specific kind of database. They should be able to choose to use either Mongodb, Postgres, Mariadb, Redis and so on for as many databases we have on the package.
A Mysql database server should be set up and integrated to the sign-up and sign-in functions along side the jwt-token function.
The text was updated successfully, but these errors were encountered: