Create mock routes matching current frontend

[Monstarrrr]

• Blocked by #310

Problem

For initializing the mock API and know if everything works with the front-end, we need to create the currently existing production routes in the Mock API

Current routes:

• [x] No auth @Monstarrrr
  • [x] POST /auth/users --> Handle form errors (mapping to form fields)*
  • [x] POST /auth/jwt/create
  • [x] POST /auth/users/activation
  • [x] POST /auth/jwt/refresh
  • [x] GET /api/posts (all)
  • [x] GET /api/posts (self)
  • [x] GET /api/posts/[id]
  • [x] GET /api/posts?type=[TYPE]
• [x] Auth --> Handle checking if the user token is valid in a middleware @ndharmateja
  • [x] GET /auth/users/me @Monstarrrr @ndharmateja
  • [x] DELETE /auth/users/me @Monstarrrr @ndharmateja
  • [x] POST /api/posts @Monstarrrr @ndharmateja

Solution

Create 'em

*Field errors are sent the following way:

{
  "fieldName1": [ "Error message 1", "Error message 2" ],
  "fieldName2": [ "Error message 1" ]
}

Global errors are sent the following way:

{
  ???
}

[Monstarrrr]

I'm on it

[Monstarrrr]

I have a problem with the authenticator middeware which is that I don't know beforehand if i'm verifying an access or refresh token, but the jwt.verify(token) throws an error if it fails so i'm trying to not make the jwt.verify(accessToken) crash the route if accessToken is invalid so I can try with the refreshToken but I haven't been able to yet.

Update: actually I think it should be handle automatically by the client making a request to refresh the token if accessToken isn't valid anymore so checking for an accessToken only is the normal behaviour