Fix TextInput two-way binding issue

• Explore repository structure and understand the issue
• Identify the root cause in OnParametersSet method
• Implement fix by tracking parent value changes separately
• Verify fix with existing tests (all 88 tests pass)
• Run all tests to ensure no regressions
• Format code according to project standards
• Remove unused _lastSetValue field per code review feedback

Summary

Fixed the TextInput component to properly preserve user input when the parent component re-renders without updating the Value parameter. This resolves the issue where user input was being reset during UI refreshes.

Root Cause

The OnParametersSet() method was comparing the incoming Value parameter against _lastSetValue, which gets updated by both:

1. User input (via HandleInputAsync)
2. Parent parameter updates (via OnParametersSet)

This caused user input to be incorrectly reset when the component re-rendered with the same parent value.

Solution

Introduced _lastIncomingValue field to track values received from the parent via the Value parameter. Now OnParametersSet() only updates the internal value when the Value parameter actually changes from the parent, preserving user input across re-renders.

The original _lastSetValue field was removed as it became redundant after the fix.

Changes Made

• File: src/RazorConsole.Core/Components/TextInput.razor
  • Added _lastIncomingValue field to track incoming parent values
  • Removed unused _lastSetValue field (4 assignments removed)
  • Updated OnParametersSet() to compare against _lastIncomingValue
  • Added comment explaining the fix

Testing

✅ All 88 existing tests pass on both .NET 8.0 and .NET 9.0
✅ Code formatted according to project standards
✅ Backward compatible with components using @bind-Value or explicit ValueChanged callbacks

How It Works Now

Scenario 1: Two-way binding with @bind-Value

• Works as before - parent value stays in sync with user input

Scenario 2: One-way binding with just Value (the bug scenario)

• User input is now preserved across re-renders
• Parent can still update the value by changing the Value parameter

Scenario 3: Parent updates value

• Component correctly updates to show the new parent value

• Fixes Value property of TextInput is not two-way binding #57

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.