What should saving a note respond with?

POST /notes responds 201 with the note you just created. Build the id with makeId() from the same file, and GET /notes/:id should be able to read that note back.

How do I verify this API?

Run npm test, which uses supertest. Assert not only that creating returns 201, but also that reading the same id right after creation returns the note you stored.

Can I change the store (note.repo.ts)?

No. Keep note.repo.ts and the global handler in app.ts exactly as given. The place you fill in is the two routes inside registerNoteRoutes.

Note Create and Read API

Your task

Build an API that creates a note and reads it back. Saving a note responds with 201, and a saved note can be found by id. Complete the two routes (POST /notes, GET /notes/:id) inside registerNoteRoutes. Note: save with noteRepo.save, read with noteRepo.findById, make ids with makeId() from the same file. POST /notes takes { title, body }.

Ground rules

•Register the routes with router.post/get inside registerNoteRoutes(router).
•Create the id with makeId() from the same file.
•Use the note store (note.repo.ts) exactly as given.
•Leave the app's global error handler (the 4-argument middleware in app.ts) as is.

Not required

•Authentication, authorization, pagination, sorting.
•The store implementation (use the given in-memory repo as is).
•Database and external-service integration.

▶About this challenge

Complete an Express + TypeScript API that creates a note and reads it back. POST /notes takes { title, body }, saves it, and responds 201; GET /notes/:id finds the saved note by id and returns it. Leave the store and global handler as given and fill in the two routes.

A data-creating API usually has two steps — save, then respond. This problem is about whether what you just created carries through to a later lookup — reading the same id back returns the same note. The habit that matters is confirming that creating a note responds 201 with the created note, and that a GET by that id returns the note you stored.

What should saving a note respond with?: POST /notes responds 201 with the note you just created. Build the id with makeId() from the same file, and GET /notes/:id should be able to read that note back.
How do I verify this API?: Run npm test, which uses supertest. Assert not only that creating returns 201, but also that reading the same id right after creation returns the note you stored.
Can I change the store (note.repo.ts)?: No. Keep note.repo.ts and the global handler in app.ts exactly as given. The place you fill in is the two routes inside registerNoteRoutes.

Note Create and Read API

Your task

Ground rules

•Register the routes with router.post/get inside registerNoteRoutes(router).
•Create the id with makeId() from the same file.
•Use the note store (note.repo.ts) exactly as given.
•Leave the app's global error handler (the 4-argument middleware in app.ts) as is.

Not required

•Authentication, authorization, pagination, sorting.
•The store implementation (use the given in-memory repo as is).
•Database and external-service integration.

▶About this challenge

What should saving a note respond with?: POST /notes responds 201 with the note you just created. Build the id with makeId() from the same file, and GET /notes/:id should be able to read that note back.
How do I verify this API?: Run npm test, which uses supertest. Assert not only that creating returns 201, but also that reading the same id right after creation returns the note you stored.
Can I change the store (note.repo.ts)?: No. Keep note.repo.ts and the global handler in app.ts exactly as given. The place you fill in is the two routes inside registerNoteRoutes.