- Add an example of how to get everything up an running with a PostgreSQL database.
- Cleanup code and make it less trash. (ongoing)
- Should we handle non-200 error responses from SuperTokens?
- (These errors likely will not happen unless someone tries to interact with our app OUTSIDE of the UI we offer. In such cases, it may not make sense to give descriptive error messages? Our app is not an API. Remix has error boundaries... so maybe we just leave it to Remix?)
- Maybe add types for
Remix Context/User? - "Field is not optional" is a bad notification for screen readers because it is too ambiguous when the message is announced.
- Especially scrutinize
login.tsxandreset-password.tsxfor cleanup.- Routes checklist:
-
/auth/session/refresh -
/ -
/login -
/logout -
/private -
/reset-password
-
- Routes checklist:
- Should we handle non-200 error responses from SuperTokens?
- REPLACE the
SuperTokensgetAllCORSHeadersmiddleware function with an implementation that does not require using middleware if possible. (We need this for things likeSvelteKitandSolidStart). (Is this needed?)