Input fields

[jwillenbring]

As a ECP SDK lead I want the ability to accept input concerning community policy compatibility so that the compatibility evidence can be evaluated, rather than just asking for a yes/no response.

Parent	Children	Related	Blocks	Depends On

Acceptance Criteria:

Tool can accept and store input responses beyond yes/no.

Description, Additional Detail, Context:

Types of responses we would want to accept include:

1. Free form text. This could be up to a paragraph or two, or as short as a word or two. It would be nice to be able to customize the size of the box to the expected length of the text - for example, a long (~10 lines) and a short (1-2 lines) option.
2. URLs. Not sure if this needs to be distinct from a text field. It would be nice to validate a validly formed URL. Also not sure if we should add additional URLs when necessary, or if we should allow multiple URLs in a single field.
3. Some of these fields might be conditional. For example, a yes/no response concerning the existence of some documentation might take a URL associated with "yes" response, but this field would not be required for a "no" response.
4. emails. Not sure if this needs to be distinct from a text field. It would be nice to validate a valid email though.
5. ?

Implemented By Task(s):

• Task: TBD