forms

🚀 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?

reproduce:

• try a schema without "properties" keyword in the playground
• and a initial-formData of type object ...

=> make sure the formData is a string to have it fixed

Warning: Failed prop type: Invalid prop `value` supplied to `TextWidget`.
    in TextWidget
    in Unknown (created by StringField)
    in StringField (created by SchemaField)
    in div (created by WrapI

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

https://material.io/resources/color/#!/?view.left=1&view.right=0 readability needs to be possible almost universally ideally. This means avoiding all caps strings in titles as screen readers read every letter and other nonsense like this however the first and foremost concern is just simply that we ship with a default that is visible for our sighted users who may have issues with color blindness