You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(apollo-wind): Text area stays one line at design time and grows at runtime - #1460
At design time every field type is the same one-line control; a Text area
now starts at one line too and grows with its content up to eight lines.
The multi-line box is for the runtime form, not the authoring row.
…gn time
Design time uses the same one-line control for every field type, so a
Text area no longer grows: floor and ceiling are both one row, and it
leaves the grow layout. Content scrolls inside the box; it stays a
textarea so line breaks in a saved value survive.
Sahil-Wakode
changed the title
fix(apollo-wind): start a QuickFormField Text area one line tall
fix(apollo-wind): keep a QuickFormField Text area at one line at design time
Oct 23, 2026
Per-package coverage and bundle size on this PR. New-line coverage = of the source lines this PR adds or changes, the % hit by tests.
Package
Coverage
New-line coverage
Packed (gzip)
Unpacked
vs main
@uipath/apollo-core
—
—
42.02 MB
50.17 MB
±0
@uipath/apollo-react
58.4%
75.0% (15/20)
8.14 MB
32.17 MB
±0
@uipath/apollo-ui-icons
—
—
2.86 MB
6.97 MB
±0
@uipath/apollo-vertex
—
—
—
—
—
@uipath/apollo-wind
79.4%
100.0% (1/1)
810.8 KB
4.68 MB
+85 B
@uipath/ap-chat
85.8%
—
40.42 MB
45.71 MB
±0
"Coverage" is each package's own coverage.include scope (e.g. apollo-core instruments only scripts/). "Packed"/"Unpacked" come from npm pack --dry-run and only cover built packages — "—" means not measured this run (package not affected / not built). "vs main" is the packed (gzipped) delta against the last successful main build (the package-sizes artifact from the Release workflow); "—" there means no main baseline was available this run. The baseline is main's latest build, not this PR's exact merge-base, so it includes any drift since the branch diverged. Packages with no vitest config are omitted.
A MetadataForm textarea started at four rows and scrolled past them. It
now starts at the same height (minRows, else rows, else 4) and grows with
its content up to maxRows (new, default 8) before scrolling. The ceiling
never sits below the floor, so a field asking for 10 rows still starts at
10.
Sahil-Wakode
changed the title
fix(apollo-wind): keep a QuickFormField Text area at one line at design time
feat(apollo-wind): Text area stays one line at design time and grows at runtime
Oct 23, 2026
Always passing maxRows enables content-based resizing on every keystroke, but the shared Textarea only preserves manual resizing when the height exceeds that ceiling (textarea.tsx:197–204). With short, one-line content, dragging a default runtime field to four rows leaves the manual-resize flag unset, so the next keystroke shrinks it back to one row. Previously, rows/minRows-only fields did not refit their height on input. Detect and preserve user-selected heights below the auto-grow ceiling as well, and add a regression test that drags to fewer than eight rows before typing.
Preserve vertical resizing for grouped runtime textareas
Runtime textareas with valueModes, headerActions, menuActions, or a badge render inside ModeAwareField's InputGroup. On this path, Textarea merges IN_GROUP_CLASS (resize-none) after its managed resize-y, removing the corner handle. These fields now auto-grow to the configured ceiling but cannot be dragged beyond it. Explicitly enable vertical resizing on this runtime control, leaving the design-time QuickFormField fixed, and add a grouped-field regression test.
The drag handle already lets a reviewer make the box as tall as they
need, so the eight-row auto-grow ceiling, the new maxRows option and
its serializer support are removed. A form textarea starts at one row
and keeps its resize handle.
Design time needs only rows={1}: min/maxRows switch on auto-sizing a
fixed box never uses. Runtime inlines the helper as one rows value used
for both rows and minRows.
The reason will be displayed to describe this comment to others. Learn more.
Would be good to validate this, I would lean towards not changing field-control behavior right now. It already has drag to resize capability. If you do want to change it, can you please give a clear example of the use case where the change is necessary / desired?
The reason will be displayed to describe this comment to others. Learn more.
Would be good to validate this, I would lean towards not changing field-control behavior right now. It already has drag to resize capability. If you do want to change it, can you please give a clear example of the use case where the change is necessary / desired?
The reason will be displayed to describe this comment to others. Learn more.
We might want to have the text area expandable still (either via drag handle or automatically), but start at one line. See attachment for the experience locking to one line.
I see this as helping the developer to see what the end user will see.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sahil-Wakode
changed the title
Design time: a Text area looks and behaves exactly like a Text field. No difference.
Runtime: a Text area is expandable. Drag its corner to make it bigger.