How do you read a search query in NestJS?

You read the query values and commonly define their expected shape as a DTO class. A search request shaped like {field, value} is handed to your handler that way.

How does the search request arrive?

It arrives in the shape {field, value} — for example field 'email' or 'name' with the value to match. You take that, look up the in-memory store, and return the matching users.

How do you verify a search API?

Confirm a normal search works: search by email and by name and check that the matching users come back. supertest lets you issue real HTTP requests and inspect the response.

Admin User Search API

Your task

Add a user search feature to the admin console. When an operator searches by email or name, show the matching users. Complete search.

Ground rules

•The search query arrives in the shape {field, value} (sent by the operator console).
•Use the in-memory user store (repo) as given.

Not required

•Authentication, sessions, and authorization (assume an already-authenticated operator is calling).
•Pagination, sorting, and search performance.
•The store implementation (use the given in-memory repo as is).

▶About this challenge

This challenge has you build a user search API for the admin console in NestJS. You complete search so that when an operator searches by email or name, the matching users are shown. The search query arrives as {field, value} and you use the given in-memory store, practicing the flow of taking a search request and turning it into a response.

This problem is about taking a search request shaped like {field, value} and returning the users that match. You read the search request, look the users up in the given in-memory store, and respond with the matches. Verifying an API like this means confirming that a normal search works — that searching by email and by name each returns the matching users.

How do you read a search query in NestJS?: You read the query values and commonly define their expected shape as a DTO class. A search request shaped like {field, value} is handed to your handler that way.
How does the search request arrive?: It arrives in the shape {field, value} — for example field 'email' or 'name' with the value to match. You take that, look up the in-memory store, and return the matching users.
How do you verify a search API?: Confirm a normal search works: search by email and by name and check that the matching users come back. supertest lets you issue real HTTP requests and inspect the response.

Admin User Search API

Your task

Add a user search feature to the admin console. When an operator searches by email or name, show the matching users. Complete search.

Ground rules

•The search query arrives in the shape {field, value} (sent by the operator console).
•Use the in-memory user store (repo) as given.

Not required

•Authentication, sessions, and authorization (assume an already-authenticated operator is calling).
•Pagination, sorting, and search performance.
•The store implementation (use the given in-memory repo as is).

▶About this challenge

How do you read a search query in NestJS?: You read the query values and commonly define their expected shape as a DTO class. A search request shaped like {field, value} is handed to your handler that way.
How does the search request arrive?: It arrives in the shape {field, value} — for example field 'email' or 'name' with the value to match. You take that, look up the in-memory store, and return the matching users.
How do you verify a search API?: Confirm a normal search works: search by email and by name and check that the matching users come back. supertest lets you issue real HTTP requests and inspect the response.