form

🚀 Feature request

Current Behavior

The type ErrorMessage doesn't have an id property.

Desired Behavior

It'd be nice id?: string would be added to the type ErrorMessage and set on the outermost component that serves as error message.

Suggested Solution

Add id={this.props.id} to the outer component in ErrorMessage.

Who does this impact? Who is this

Are you submitting a bug report or a feature request?

Bug? I guess.

What is the current behavior?

Bug Report

The following field (without a validator) cannot be updated via the model. No errors or warnings are logged:

{ "label":"ANR",
  "model":"or.anr",
  "type":"checklist",
  "listBox":true,
  "values": [
      {"name":"a", "value":[1,2]},
      {"name":"b", "value":[2,2]}
   ] }

model.or.anr = [[1,2]]; // fails to check "a"

If you would like a jsfiddle demo, let

Add singular form of the following:

getErrors() -> getError()
getWarnings() -> getWarning()

The idea is to return the first error/warning of a field, instead of an array.
Unlike getErrors/getWarnings that can either take 0 or 1 arguments, getError/getWarning must receive a field name.

Function signature:

function getError(fieldName: string): string;
function getWarning(fieldNam