• Tags
  • seed data (delegated to #30 )
  • GET /tags/search

GET /tags/search?q=<pattern> should return a list of tags that matches the pattern

• GET /users/me

Hi Alex @RecklessPotcover,

1. Data labeled in red, are they available? If so, what's the key? If not, when and where will they be?

• See Zeplin.

2. When will the "Organisation" API be available?

• Which API are you asking about specifically? Atm, we have GET /organization/:id (on master).

3. The "Related Positions" in the Position page, will it be an individual API? If not, when and where will it be?

• We do not have related positions for now. And we have not discussed it.

4. How is the progress of the APIs of the profile page?

• See Zeplin
  • What is finished:
    • GET /applications/me
  • Work in progress:
    • GET /users/me does not provide enough info for now - missing profile pic & age. Can add them shortly and let you know when done.
    • GET /posts/me is not ready yet. We will let you know when done.
    • We will add another request to get the number of applications of a user: GET /applications/me/count

5. Have you guys decided how to store and transfer the content of the position description? (For this one I've discussed with Jay and got an initial solution. If u guys have not decided yet, we can talk about it during tomorrow's Studio.)

• Jay and I (Nathan) have talked about it a while ago. Jay suggested going with CKEditor. We will store the HTML as string in the database.

In the future, if there is any problem regarding the backend, please create new issues on Github so that I and Luca are informed and can give you answers asap, as both of us need to work on different things and teams is not necessarily the best platform to discuss these sort of things. (I hate teams with a passion). Also, Github issues are good for separating different issues than messaging.

• Posts
  • seed data
  • GET /posts/me

Gather some real data for these attributes:

• Organization
  • name
• Event
  • name
  • location
• Position
  • name
  • types of work

Criteria:

• Names of event and corresponding positions must sound connected.
• Locations should be real addresses in Brisbane, QLD. Use this website to validate the address.

Inspirations: Refer to these websites for ideas.

Files: create these files in /prisma:

• tags.json

[
  "..."
]

• data.json

[
  {
    organization: {
      name: "...",
      events: [
        {
          name: "...",
          location: "...",
          positions: [
            name: "...",
            tags: [
              "...", "..."
            ],
          ],
        }
      ]
    }
  }
]

• Look into JWT

• GET /events/{eventId}
• GET /organizations/{organizationId}
• GET /positions/{positionId}

Info

• Project type: Node.js back-end

Stack

• Language: TypeScript
• Framework: Express
• Database: PostgreSQL
• ORM: Prisma
• Testing: Jest

Prisma ORM

Features:

• Seeding
• Migrating

Readings:

• Prisma vs TypeORM
• Example of Prisma in a project

Testing

• Jest doc
• Jest & Supertest for Express

Dependencies

Dependencies

• body-parser: body parsing middleware

Dev Dependencies

• nodemon: auto-reload (nodemon alternative)
• dotenv: environment variables loader
• eslint
• prettier
• prisma: ORM
• jest: testing framework
• supertest: testing framework for HTTP requests

Workflow

Follow Github flow

References

• microsoft/TypeScript-Node-Starter

TODO

• Create a dummy api

• GET /applications/me

Joi documentation

• GET /positions

• Request: POST /auth/login
• Body: (arbitrary input)

{
  "email": "[email protected]",
  "password": "123456"
}

• Client: Insomnia

• Log:

be-creamcats | [1] INFO [1631515857115] (170 on 7e81991919c4): request completed
be-creamcats | [1]     res: {
be-creamcats | [1]       "statusCode": 401,
be-creamcats | [1]       "headers": {
be-creamcats | [1]         "x-powered-by": "Express",
be-creamcats | [1]         "access-control-allow-origin": "*",
be-creamcats | [1]         "content-type": "application/json; charset=utf-8",
be-creamcats | [1]         "content-length": "139",
be-creamcats | [1]         "etag": "W/\"8b-TH8AXdnwSAUcpvp3uF+OhT0UmUU\""
be-creamcats | [1]       }
be-creamcats | [1]     }
be-creamcats | [1]     responseTime: 119
be-creamcats | [1]     req: {
be-creamcats | [1]       "id": 1,
be-creamcats | [1]       "method": "POST",
be-creamcats | [1]       "url": "/auth/login",
be-creamcats | [1]       "query": {},
be-creamcats | [1]       "params": {},
be-creamcats | [1]       "headers": {
be-creamcats | [1]         "host": "localhost:6400",
be-creamcats | [1]         "user-agent": "insomnia/2021.5.2",
be-creamcats | [1]         "content-type": "application/json",
be-creamcats | [1]         "accept": "*/*",
be-creamcats | [1]         "content-length": "51"
be-creamcats | [1]       },
be-creamcats | [1]       "remoteAddress": "::ffff:172.18.0.1",
be-creamcats | [1]       "remotePort": 35950
be-creamcats | [1]     }
be-creamcats | [1] Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
be-creamcats | [1]     at ServerResponse.setHeader (_http_outgoing.js:561:11)
be-creamcats | [1]     at ServerResponse.header (/app/node_modules/express/lib/response.js:771:10)
be-creamcats | [1]     at ServerResponse.send (/app/node_modules/express/lib/response.js:170:12)
be-creamcats | [1]     at ServerResponse.json (/app/node_modules/express/lib/response.js:267:15)
be-creamcats | [1]     at apiErrorHandler (/app/dist/components/errors/errors.controllers.js:15:28)
be-creamcats | [1]     at Layer.handle_error (/app/node_modules/express/lib/router/layer.js:71:5)
be-creamcats | [1]     at trim_prefix (/app/node_modules/express/lib/router/index.js:315:13)
be-creamcats | [1]     at /app/node_modules/express/lib/router/index.js:284:7
be-creamcats | [1]     at Function.process_params (/app/node_modules/express/lib/router/index.js:335:12)
be-creamcats | [1]     at next (/app/node_modules/express/lib/router/index.js:275:10)

• GET /applications/me/count
• Add profile pic and age to the user schema