🛠️ [TASK] : User Input Component - Plain Text

[mike-mcnulty]

Summary

As a proposer, I need to be able to input short plain text responses, so that I can provide succinct unstructured details about my proposal.

Use Cases:

• Proposer Name
• Co-proposers and additional applicants
• Title
• Problem Statement
• Solution Statement

Acceptance Criteria

• Default values should be static placeholder that helps proposer provide answer (configured by admins)
• In Editing mode, default value should disappear when user starts editing field
• User cannot save responses until all required fields have been completed in the section
• If user leaves an optional field blank then the saved component should show ...(@seankdesigns we need a bit of thinking on this. i have the co-proposer field in mind looking at this designs. perhaps this makes more sense as a conditional behind something like "is proposal just you or with a team?" to avoid empty responses)
• While editing is active, users can view their current character count vs the character limit (@seankdesigns all the char count stuff in this and following bullets missing from design for plain text. was this intentional? seems relevant)
• User may enter characters beyond the character limit, but cannot save while char_count > char_limit
• Any text entered beyond the character limit should be shown to the user as red text to indicate the overflow to the user

Designs

https://www.figma.com/design/1e1MMDXyi0oL9sG9IunWL7/UI-Kit-Figma-for-catalyst?node-id=5271-49626&t=gTh3B1j2eYONQrjf-0

Default

Selected

Editing

Filled

[seankdesigns]

@mike-mcnulty Updated designs and added to ticket. RE char count - There was no limit listed for these fields in the template doc. Should a limited be added and if so, what is that limit?

RE optional fields: For this question I'd suggest a dropdown with options for:

• Individual
• Entity

If Individual: no additional field.
If entity: Show additional text field "List co-proposers and additional applicants"

[seankdesigns]

Could potentially flip the order too?

[dtscalac]

@mike-mcnulty

User may enter characters beyond the character limit, but cannot save while char_count > char_limit

It's less effort to don't allow to enter beyond the character limit, the default text field behavior is to truncate the text at character limit.

[mike-mcnulty]

@dtscalac highly desirable to have this behavior. current frustration today in ideascale is exactly what you describe - the field truncates to char limit, making it effectively unusable as a scratch pad for ideating / refinement. this is a driver of the behavior we want to avoid where user feels they need to leave the application in order to actually do their writing