massover / jaypeak Goto Github PK

• Users should log into the website with their email, not username.

• Usernames for yodlee should be dynamically generated on the user model.

• Display password contstraints:

  Password must be at least 8 characters long and contain at least one upper case letter,
  one number and any of these special characters !@#$%^&*() ].

• Remove the remember me box.

• Remove username from registration form

Build a SPA experience for registration, adding accounts, and finding recurring transactions

• Add profile page (where you can delete an account)
• Add a link to fastlink
• Add a logout link

When a user is first logged in (ie, they have not connected any accounts to yodlee), they should be shown the fastlink page to connect their accounts.

When a user logs in and we kick off an aysnchronous celery task
Then the user should see Loading until the task is complete
And then the user should be redirected to /recurring-transactions

In synchronous server side templating land, we can accomplish this by:

• redirecting the user to a different route(eg, /login/sync-transactions)
• the template will have a loading icon
• the template contains javascript which just polls the sync-transaction endpoint until it returns a complete state
• when the state is complete, it does a javascript redirects /recurring-transactions

In asynchronous land, we can accomplish this by:

• we create a different /login endpoint that returns a 200/401 on success/failure.
• upon success we update the dom with the loader
• when the state of the 'task' model to changes from pending -> complete, we redirect to /recurring-transactions

The behavior is broken right now because it immediately redirects without waiting for the task to complete.

The task must be an asynchronous worker because it could take longer than 30 seconds to complete and heroku times out web requests after 30 seconds.

After ci passes, after a deploy, run migrations