ezzabuzaid / fayona

The Node.js version of .NetCore

ezzabuzaid/fayona Issues

Improve validation model state
Closed a year ago
Resolve tsconfig path out of the box
Closed 2 years ago1
Create postman collections from metadata
Closed 2 years ago
Use tslog as internal logging tool
Updated 2 years ago
Refactor Identity
Updated 2 years ago
the profile object should has a default value in the service
Closed 4 years ago
Should be protected not public
Closed 4 years ago
create the profile / account strategy
Closed 4 years ago
replace the response with login response and not user info
Closed 4 years ago
update this field to be ProfileSchema instead
Closed 4 years ago
Instead of invoke this function in hook invoke it in password setter
Closed 4 years ago
make an interface for user token
Closed 4 years ago
Move it to each crud operation without the [attr] key
Closed 4 years ago
the `type` property should be in the `options` type
Closed 4 years ago
constructor(schema: Schema) { }
Closed 4 years ago
use pipline to move files instead of sync way
Closed 4 years ago
call load function implicitly in envirnoment load method
Closed 4 years ago
Security
Closed 4 years ago
use localization here
Closed 4 years ago
setup delete folder functions
Closed 4 years ago
hooks should be called
Closed 4 years ago
all calls should be run within transaction
Closed 4 years ago
add transaction
Closed 4 years ago
imporve error handling, if id is not string throw directly
Closed 4 years ago
imporve error handling, check the types of query
Closed 4 years ago
imporve error handling, if ids is not list of string throw directly
Closed 4 years ago
create member and group should be within transaction
Closed 4 years ago
you can easily move the creation logic from the group router to be used here
Closed 4 years ago
Generic SchemaType should inherit from RepoHooks interface which
Closed 4 years ago
Before any query or write check the body to met the model to avoid [injections] ...
Closed 4 years ago
model validation should be in repo
Closed 4 years ago
query validation should be in service
Closed 4 years ago
normalize the mobile number in order to ensure the uniqueness
Closed 4 years ago
for each write operation should have a transaction option,
Closed 4 years ago
find a way to know that the token is really for this user (unique device id) gen...
Closed 4 years ago
invalidate the refresh token directly after new one is generated
Closed 4 years ago
the user should verify his email and phonenumber
Closed 4 years ago
Validate the body to meet the schema exactly using reflect metadata
Closed 4 years ago
Replace them with fixture function to check if it has a value
Closed 4 years ago
Move it to fixture folder
Closed 4 years ago
provide an option for strict schema checking to not allowed
Closed 4 years ago
use reflect metadate instead of conditions
Closed 4 years ago
save the user device, so the next time when he logged from another time you'll n...
Closed 4 years ago
save the device id in token so when the user request refresh token,
Closed 4 years ago
find a way to know that the token is really for this user (unique device id) gen...
Closed 4 years ago