Features needed in order to get to 1.0
samuelgozi opened this issue · 2 comments
samuelgozi commented
Important: If you plan to contribute to any of these tasks, please comment before you start!
This issue tracks all of the features needed in order to get to version 1.0.
The code is pushed to the official-feature-parity branch.
All of the REST API features:
- Exchange custom token for an ID and refresh token
- Exchange a refresh token for an ID token
- Sign up with email / password
- Sign in with email / password
- Sign in anonymously
- Sign in with OAuth credential
- Fetch providers for email
- Send password reset email
- Verify password reset code
- Confirm password reset
- Change email
- Change password
- Update profile
- Get user data
- Link with email/password
- Link with OAuth credential
- Unlink provider
- Send email verification
- Confirm email verification
- Delete account
samuelgozi commented
Additional Tasks:
Make sure that the next methods verify that the idToken hasn't expired before making the request and that the user is logged in.
- Change email
- Change password
- Update profile
- Get user data
- Link with email/password
- Link with OAuth credential
- Unlink provider
- Send email verification
- Delete account
It's also important to be able to listen for a state change.
- Implement some kind of event dispatcher for listening to state changes.
samuelgozi commented
Optional tasks:
- Migrate to Typescript(Check how it affects bundle size)
- Fully test the library(optional because I still don't know if mocking the responses is a good idea)