add solution #2911
add solution #2911
Conversation
There was a problem hiding this comment.
Great job on your submission! 🎉 The code is well-structured and meets the task requirements. While there are a couple of minor improvements suggested, such as verifying the UserInfo component's implementation and considering the removal of the unnecessary name property in TodoProps, these do not impact the functionality. Keep up the good work and continue refining your skills! 😊
✨ Please rate this review in the Platform's notification center. I will be grateful for your feedback! ✨
| title: string; | ||
| userId: number; | ||
| completed: boolean; | ||
| name: string; |
There was a problem hiding this comment.
The name property in TodoProps might be unnecessary since the name is derived from the user data when creating a new todo. Consider removing it from the TodoProps type.
| <option value="0" disabled> | ||
| Choose a user | ||
| </option> | ||
| <UserInfo users={usersFromServer} /> |
There was a problem hiding this comment.
The UserInfo component is used here as if it returns a list of <option> elements. Ensure that UserInfo is implemented to return the correct JSX structure for rendering user options. If UserInfo is not a component that returns JSX options, you may need to map over usersFromServer directly to generate the <option> elements.
DEMO LINK