Change the onChange callback on phone input

[skrobek]

PR Type

bug_fix

---

Description

• Fixed the onChange callback behavior in the PhoneInputField component by replacing the useEffect hook with a direct onPhoneUpdate callback.
• Simplified the phone number update logic to ensure proper handling of changes.
• Updated the package version in package.json to 0.1.86.

---

Changes walkthrough 📝

	Relevant files
Bug fix	PhoneInputField.tsx Refactor phone input field to fix onChange callback behavior src/atoms/phoneInputField/PhoneInputField.tsx Replaced the useEffect hook with a direct onPhoneUpdate callback to handle phone number updates. Simplified the logic for updating the phone number by removing redundant code. +3/-4
Configuration changes	package.json Bump package version to 0.1.86                                                      package.json Updated the package version from 0.1.85 to 0.1.86. +1/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Code Refactor The new implementation using onPhoneUpdate directly in the usePhoneInput hook should be thoroughly tested to ensure it handles all edge cases previously covered by the useEffect hook.

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
General	Add type annotations to the onPhoneUpdate callback to ensure type safety Ensure that the onChange event handler is properly typed to prevent runtime errors. TypeScript should be used to define the type of the phone parameter and the expected structure of the object passed to onChange. src/atoms/phoneInputField/PhoneInputField.tsx [82-84] -onPhoneUpdate: (phone) => { +onPhoneUpdate: (phone: string) => { onChange({ target: { value: phone } }) } Suggestion importance[1-10]: 7 Why: Adding type annotations enhances type safety and helps prevent potential runtime errors, which is crucial in TypeScript projects. The suggestion correctly identifies the need for typing the phone parameter in the onPhoneUpdate function.	7