when you create a route that gives us information about a toy listing, you will return information about the toy information, but part of it also includes the id of the user that posted the toy, so we need information about that user, not only the user id, we need the first name of the user last name email etc.. all of that information is stored in the User entity, so you will join the Toy listing and User collection and return information from both so that we can use that information on the client side.
everywhere you see ids you should return information that relates to the ids in the corresponding entity.
when you create a route that gives us information about a toy listing, you will return information about the toy information, but part of it also includes the id of the user that posted the toy, so we need information about that user, not only the user id, we need the first name of the user last name email etc.. all of that information is stored in the User entity, so you will join the Toy listing and User collection and return information from both so that we can use that information on the client side.
everywhere you see ids you should return information that relates to the ids in the corresponding entity.