Resolved the OtpInput value mismatch issue for input types text and password.

[KishoreJey]

Root Cause of the Issue

The internal logic for the SfOtpInput component's Value property was including non-printable control characters (specifically, null characters like \0) in its string representation. These characters were likely used as internal placeholders for empty OTP cells. When the ValueChanged event was triggered, these control characters were included in the NewValue and OldValue properties of the event arguments. This caused the reported values to be incorrect (e.g., "1a\0\0" instead of "1a"), leading to a data mismatch and unexpected behavior when consuming the event.

Description of Change

• To resolve this, the OnValuePropertyChanged method has been updated to sanitize the OTP values before the ValueChanged event is raised.
• The implementation now explicitly filters both the oldValue and newValue strings to remove any control characters.
• This ensures that the OtpInputValueChangedEventArgs passed to the user contain only the actual visible characters that have been entered.
• This change guarantees clean and accurate string data in the event, resolving the value mismatch issue for all input types, including Text and Password.

Issues Fixed

Issue : #184

[Copilot]

Pull Request Overview

This PR fixes a value mismatch issue in the SfOtpInput component where control characters (like null characters) were being included in ValueChanged event arguments, causing incorrect reported values. The fix ensures that only visible characters are passed to event handlers for all input types.

• Removes conditional logic that only sanitized control characters for Number input type
• Applies control character filtering to all OTP input types (Text, Password, Number)
• Simplifies the event raising logic by using sanitized values consistently

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The null check for ValueChanged is redundant since the subsequent call uses the null-conditional operator (?.). Consider removing this if statement and just calling RaiseValueChangedEvent directly, as the method already handles null events safely.

[PaulAndersonS]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).