add task solution

[illyaSmyk]

No description provided.

[mateacademy-ai-mentor]

Review Summary

I am approving your solution because all functional requirements are correctly implemented: the Person component behaves as expected for all three people, age is treated as optional, and marriage/partner wording and class names are correct. The remaining issues are checklist‑style concerns around destructuring and ternary formatting, but they do not break functionality or block task completion. To align better with [CHECKLIST ITEM #1], consider fully destructuring the person prop inside Person.jsx, e.g. const { name, age, sex, isMarried, partnerName } = person;, and then use name, age, etc. directly instead of person.name, person.age, and so on. For readability and [CHECKLIST ITEM #2] and [CHECKLIST ITEM #3], you can compute the partner role in a separate variable before JSX, for example const partnerRole = sex === 'm' ? 'wife' : 'husband';, and then use that variable in the template literal instead of an inline ternary. Overall, your logic is solid and matches the task requirements; the suggested changes are style improvements that will help you better follow the provided checklist and keep your React components cleaner going forward.

---

✨ Please rate this review in the Platform's notification center¹. I will be grateful for your feedback! ✨

Footnotes

1. Rate AI review example ↩

[mateacademy-ai-mentor]

This violates checklist item #1: "Use destructuring for getting access to values of props object". You destructure { person } but then repeatedly access person.name, person.age, etc. Instead, destructure the needed fields from person (e.g. const { name, age, sex, isMarried, partnerName } = person;) and use them directly.

[mateacademy-ai-mentor]

This violates checklist item #1: "Use destructuring for getting access to values of props object". Instead of accessing person.name, person.age, etc. directly from person, destructure the needed fields (name, age, sex, isMarried, partnerName) from the person prop.

[mateacademy-ai-mentor]

This line uses person.age inline and relies on truthiness for conditional rendering. Combined with other inline person usages, it conflicts with checklist item #1, which requires destructuring props into separate variables.

[mateacademy-ai-mentor]

This line combines person.isMarried and a ternary inside a template literal: ${person.partnerName} is my ${person.sex === 'm' ? 'wife' : 'husband'}. It violates checklist item #2 (ternary operands should be on separate lines) and checklist item #3 (avoid several cases in conditional rendering; move the condition into a separate variable). Consider computing the role (wife/husband) in a variable before JSX and formatting the ternary across multiple lines.