andela/eagle-bn-backend

Barefoot Nomad - Making company travel and accomodation easy and convinient.

Vision

Make company global travel and accommodation easy and convenient for the strong workforce of savvy members of staff, by leveraging the modern web.

---

Docker set up

. Install docker . Clone repository to your local machine and run npm install to install all dependancies . In .env file, provide variables for database GB-USER-NAME, DB-PASS and DB-DATABASE . While in development run npm run dockerDev . While in production run npm run dockerProd

Deployment

this will be deployed on heroku, To access the app on the cloud while it has been deployed use this link, Production URL

eagle-bn-backend's Issues

Create request. validate country/city

Validate country and city when request created, not yet implemented. Actually a request can be created with country: ddddd. The system doesn't check also if a city belongs to the specified country which may cause many inconsistencies

search request by time interval

when providing 'to' and 'from' query params to look for trip requests in a time interval, the system does not check if 'to' is greater than 'from'. It just considers the param 'to'

Signup validation doesn't check if password contains numbers and letters.

A user can signup with password 12345678@@ or MMMMMMM@@. Validation should check if password contains numbers and letters and at least a special character

Login with social accounts

when wrong access token provided on login with google or facebook, 500 internal server is thrown. A clear message like 'wrong access-token' and a 401 status should be sent as response

Invalid city on new trip request

When Wrong city is provided on a certain country, the app doesn't really validate it!

update request not well formatted

The user is required to provide a trip Id when updating a request. the system doesn't check if the trip id belongs to that given request. The system should update request data and trip data in different routes

update profile allows user to update some sensitive fields

When updating his profile, a user can actually:
update his Id(update profile)
his roleID (update profile)
createdAt and updatedAt fields

email Unsubscription

Wrong Unsubscription link in email pug files.
it is: /api/v1/users/unsubscribe/token
while it should be: /api/v1/users/email/unsubscribe/token