fix: resolve console errors with Textarea component

[ivan-dalmet]

Summary

• Ensure field.value is never null or undefined when passed to the Textarea, preventing React console errors about uncontrolled-to-controlled transitions and null value props.

Closes #689

Test plan

• Existing textarea field tests pass (4/4)
• Verify no console errors when rendering a Textarea form field
• Verify textarea still works correctly with default values and user input

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes
  • Enhanced textarea field behavior to handle empty states more consistently, ensuring reliable functionality across all value scenarios.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
start-ui-web-v3	Ready	Preview, Comment	Feb 20, 2026 3:13pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

Walkthrough

A single-line change adds an explicit value prop to the Textarea component, ensuring it receives either field.value or an empty string. This prevents the component from falling into an uncontrolled state and resolves a console error.

Changes

Cohort / File(s)	Summary
Textarea Value Prop src/components/form/field-textarea/index.tsx	Added explicit value prop binding to ensure Textarea remains a controlled component by defaulting to an empty string when field.value is undefined.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main fix: resolving console errors with the Textarea component by ensuring field.value is never null/undefined.
Linked Issues check	✅ Passed	The code change directly addresses issue #689 by adding an explicit value prop to prevent uncontrolled-to-controlled transitions that cause console warnings.
Out of Scope Changes check	✅ Passed	The change is minimal and focused solely on fixing the Textarea component's value handling, with no unrelated modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ivan-dalmet/fix-textarea-error

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud