Skip to content

Conversation

@kmcginnes
Copy link
Collaborator

@kmcginnes kmcginnes commented May 16, 2025

Description

Adds a basic TextArea component and renames the existing one to TextAreaField since it has validation message and a container.

Validation

  • Smoke test

Related Issues

Check List

  • I confirm that my contribution is made under the terms of the Apache 2.0
    license.
  • I have run pnpm checks to ensure code compiles and meets standards.
  • I have run pnpm test to check if all tests are passing.
  • I have covered new added functionality with unit tests if necessary.
  • I have added an entry in the Changelog.md.

@kmcginnes kmcginnes changed the title Text area component Add basic TextArea component May 16, 2025
@kmcginnes kmcginnes marked this pull request as ready for review May 16, 2025 21:45
@kmcginnes kmcginnes force-pushed the text-area-component branch 2 times, most recently from a0fff61 to 64121d8 Compare May 21, 2025 21:46
@kmcginnes kmcginnes requested a review from andreachild May 21, 2025 22:16
}

/** @deprecated Use TextArea instead */
const TextAreaField = forwardRef<HTMLTextAreaElement, TextAreaProps>(
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: ValidatedTextArea is more descriptive than TextAreaField?

Copy link
Collaborator Author

@kmcginnes kmcginnes May 22, 2025

Choose a reason for hiding this comment

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

Hmm, I'm not sure I agree. The suffix "field" is what I've used for other legacy form components that include the interactive component, the label, and a validation message. But either the TextAreaField or the TextArea component can have validation. The TextArea component just doesn't supply the label and validation message.

I chose the term "field" because forms have the concept of a fieldset. In my head, at least, I consider a field to be the input, the label, and any description text or validation errors. But maybe that's a "me" thing.

@kmcginnes kmcginnes force-pushed the text-area-component branch from 64121d8 to 27fbffb Compare May 22, 2025 20:23
@kmcginnes kmcginnes merged commit c41e671 into aws:main May 22, 2025
2 checks passed
@kmcginnes kmcginnes deleted the text-area-component branch May 22, 2025 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Separate existing TextArea from the basic component and styles

2 participants