Adjust project structure

[FoRVaiS]

Summary

Routes

• Create a centralized file for defining routes

  Response

• Create controller wrapper to automate response formatting/creation

  Pagination

• Introduce middleware to extract page and limit query params and inject them into the request object
• Add pagination links to response

Testing

1. Spin up resources: make res
2. Start the api server: npm run -w apps/api start:dev

Verify routes still work

3. Use Postman (or Thunder Client) to login with dummy admin credentials. http://127.0.0.1:3000/api/v1/auth/login
   • admin@email.com: admin
4. Expect the following response:

   {
   "isError": false,
   "data": {
   "userId": 1
   },
   "pagination": {
   "prev": null,
   "next": null
   }
   }

[FoRVaiS]

Hours Worked: 3

[tgrigoruk]

If i try a non existing route the response is 404 and contains

"isError": false,
"data": "Route Not Found"

Is this intended behaviour? It could be a problem if one checks the response for isError rather than status code.

[FoRVaiS]

If i try a non existing route the response is 404 and contains

"isError": false,
"data": "Route Not Found"

Is this intended behaviour? It could be a problem if one checks the response for isError rather than status code.

Not intended, I forgot to pass an error into the response function, fixed now.