Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Features needed in order to get to 1.0 #2

Closed
20 tasks done
samuelgozi opened this issue Mar 9, 2020 · 2 comments
Closed
20 tasks done

Features needed in order to get to 1.0 #2

samuelgozi opened this issue Mar 9, 2020 · 2 comments

Comments

@samuelgozi
Copy link
Owner

samuelgozi commented Mar 9, 2020 •
edited
Loading

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
Copy link
Owner Author

samuelgozi commented Mar 9, 2020 •
edited
Loading

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
Copy link
Owner Author

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)

samuelgozi added a commit that referenced this issue Mar 13, 2020
@samuelgozi
feat: Completed set of feature from issue #2
1b1ec9b
samuelgozi added a commit that referenced this issue Mar 15, 2020
@samuelgozi
Official feature parity (#4)
6048738 
* feat: Added features for passwork sign up and sign in, and profile management

* Update README.md

* refactor: whole last commit

* refactor: check that user is logged in on methods that require it

* refactor: Oauth flow simplified

* refactor: optimized for minimal characters count and lines of code.

* feat: Fetch providers for email

* feat: Completed set of feature from issue #2

* docs: updated Readme

* fix: fixed some small bugs

* feat: Added state change listener
@sesam sesam mentioned this issue May 6, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@samuelgozi