kadhirvelm / atlasp-backend Goto Github PK

Disable the phone number check when creating admin accounts

Updating events is not working properly

Need some way of standardizing which one to use, doing a tonnnn of iterating through arrays right now to convert between the types.

Right now if user A creates and event with user B and user C, then edits the event to remove user C, user B will still have user C on their graph. We have no way of telling whether or not user B created user C or not

All the linters are fighting each other, fix them using some tslint config/plugin

Right now the DB does not check if a user is premium before categorizing people, it should definitely be checking that and allow basic users to add up to 10 ignore users

Changing account details and changing a user's indexed connections should go to different collections to prevent unintentional updates

Let's do a 2FA check to make sure the phone number is valid and in the users possession with a challenge. Right now if you enter anyone's phone number into the reset link field, it'll take you straight to their account

We should check to see that the user is a premium user before updating their relationships

In addition to current account details to avoid the 3 time backend call for all the needed items

To prevent non-frontend induced backend calls

https://www.npmjs.com/package/libphonenumber-js

Before creating a new user