Skip to content

fix: adjusted textarea and playground paddings and design#11635

Open
lucaseduoli wants to merge 6 commits intorelease-v1.8.0from
fix/prompt_playground_design
Open

fix: adjusted textarea and playground paddings and design#11635
lucaseduoli wants to merge 6 commits intorelease-v1.8.0from
fix/prompt_playground_design

Conversation

@lucaseduoli
Copy link
Collaborator

@lucaseduoli lucaseduoli commented Feb 6, 2026

This pull request introduces improvements to the chat input and sliding container components in the frontend, focusing on better UI responsiveness and layout consistency. The main changes include adding a resize observer for the chat input textarea, adjusting styling for text elements, and modifying container layouts to enhance usability.

Enhancements to chat input responsiveness:

UI and layout adjustments:

Previous playground and prompt:

image image image

Playground and prompt after fixes:

image image image

@lucaseduoli lucaseduoli requested a review from keval718 February 6, 2026 20:44
@lucaseduoli lucaseduoli self-assigned this Feb 6, 2026
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 6, 2026

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review

Walkthrough

The changes modify chat input components and layout styling. A ResizeObserver was added to detect textarea width changes and trigger dynamic height adjustment. CSS classes were adjusted to refine text sizing, remove padding constraints, and restructure the textarea wrapper layout.

Changes

Cohort / File(s) Summary
Chat Input Components
src/.../chat-input/components/no-input.tsx, src/.../chat-input/components/text-area-wrapper.tsx, src/frontend/src/components/ui/textarea.tsx
Added ResizeObserver to detect width-triggered textarea resizing with ref tracking; applied text-sm styling class to placeholder element; restructured textarea wrapper with height constraints.
Layout Container
src/.../sliding-container/components/flow-page-sliding-container.tsx
Removed padding from StickToBottom.Content wrapper.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 3
❌ Failed checks (1 error, 2 warnings)
Check name Status Explanation Resolution
Test Coverage For New Implementations ❌ Error PR introduces new ResizeObserver functionality and layout modifications without corresponding test coverage. While test infrastructure exists, new features lack tests. Add tests for ResizeObserver implementation, layout wrapper changes, and verify CSS class additions in existing tests.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Test Quality And Coverage ⚠️ Warning Pull request introduces significant functionality changes to textarea components and ResizeObserver logic without corresponding test coverage for modified files. Create comprehensive test files for text-area-wrapper.tsx, textarea.tsx, and flow-page-sliding-container.tsx verifying ResizeObserver functionality, styling changes, and padding modifications.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title directly addresses the main changes: adjusting textarea sizing/behavior and removing padding from playground layout components.
Test File Naming And Structure ✅ Passed PR updates four frontend components with UI/layout improvements; no test files are present, so test file naming requirements are not applicable.
Excessive Mock Usage Warning ✅ Passed PR modifies only UI/layout source files without introducing new tests or mock usage patterns.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/prompt_playground_design

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

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

@github-actions github-actions bot added the bug Something isn't working label Feb 6, 2026
Copy link
Member

@Cristhianzl Cristhianzl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

Frontend Unit Test Coverage Report

Coverage Summary

Lines Statements Branches Functions
Coverage: 18%
18.39% (5918/32166) 12.03% (3016/25070) 12.36% (855/6917)

Unit Test Results

Tests Skipped Failures Errors Time
2288 0 💤 0 ❌ 0 🔥 32.221s ⏱️

@github-actions github-actions bot added the lgtm This PR has been approved by a maintainer label Feb 6, 2026
@codecov
Copy link

codecov bot commented Feb 6, 2026

Codecov Report

❌ Patch coverage is 0% with 15 lines in your changes missing coverage. Please review.
✅ Project coverage is 35.01%. Comparing base (22607cc) to head (a258015).

Files with missing lines Patch % Lines
...t-view/chat-input/components/text-area-wrapper.tsx 0.00% 15 Missing ⚠️

❌ Your patch check has failed because the patch coverage (0.00%) is below the target coverage (40.00%). You can increase the patch coverage or adjust the target coverage.
❌ Your project check has failed because the head coverage (41.84%) is below the target coverage (60.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

Impacted file tree graph

@@                Coverage Diff                 @@
##           release-v1.8.0   #11635      +/-   ##
==================================================
- Coverage           35.02%   35.01%   -0.01%     
==================================================
  Files                1515     1515              
  Lines               72567    72582      +15     
  Branches            10934    10936       +2     
==================================================
  Hits                25418    25418              
- Misses              45755    45770      +15     
  Partials             1394     1394              
Flag Coverage Δ
frontend 16.65% <0.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...onent/chat-view/chat-input/components/no-input.tsx 100.00% <ø> (ø)
...ntainer/components/flow-page-sliding-container.tsx 0.00% <ø> (ø)
src/frontend/src/components/ui/textarea.tsx 87.50% <ø> (ø)
...t-view/chat-input/components/text-area-wrapper.tsx 0.00% <0.00%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@lucaseduoli lucaseduoli enabled auto-merge February 6, 2026 20:49
@lucaseduoli lucaseduoli disabled auto-merge February 6, 2026 20:50
@github-actions github-actions bot added bug Something isn't working and removed bug Something isn't working labels Feb 6, 2026
@lucaseduoli lucaseduoli changed the base branch from main to release-v1.8.0 February 6, 2026 20:57
@github-actions github-actions bot added bug Something isn't working and removed bug Something isn't working labels Feb 6, 2026
@github-actions github-actions bot added bug Something isn't working and removed bug Something isn't working labels Feb 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working lgtm This PR has been approved by a maintainer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants