Completing our API
In the previous chapters, we have shown you how to write unit, integration, and E2E tests as part of a TDD process. In this chapter, we've outlined the factors you should consider when designing an API. Now, we pass the baton to you to implement the rest of the API. Specifically, you should implement the following requirements:
- Delete
- User must provide a user ID to delete
- Search
- Defaults to the last 10 users who have registered
- Create
- User must provide an email address and password
- User may optionally provide a profile; otherwise, an empty profile will be created for them
- Retrieve
- When a user provides a user ID of another user, the profile of that user should be returned
- Update
- When a user provides a user ID and a complete user object, we should replace the old user object with the new one
- When a user provides a user ID and a partial user object, we should merge the partial object into the existing object
Remember to also follow our existing conventions:
- All request data must...
