FormValidator

A string containing the English text to translate.

(optional) An associative array of replacements to make after translation. Based on the first character of the key, the value is escaped and/or themed. See \Drupal\Component\Render\FormattableMarkup::placeholderFormat() for details.

(optional) An associative array of additional options, with the following elements:

• 'langcode' (defaults to the current language): A language code, to translate to a language other than what is used to display the page.
• 'context' (defaults to the empty context): The context the source string belongs to. See the @link i18n Internationalization topic @endlink for more information about string contexts.

An object that, when cast to a string, returns the translated string.

The string translation service.

The string translation service.

The request stack.

The string translation service.

The CSRF token generator.

A logger instance.

The form error handler.

An associative array containing the structure of the form.

The current state of the form. If the user submitted the form by clicking a button with custom handler functions defined, those handlers will be stored here.

A unique string identifying the form for validation, submission, theming, and hook_form_alter functions.

An associative array containing the structure of the form, which is passed by reference. Form validation handlers are able to alter the form structure (like #process and #after_build callbacks during form building) in case of a validation error. If a validation handler alters the form structure, it is responsible for validating the values of changed form elements in $form_state->getValues() to prevent form submit handlers from receiving unvalidated values.

The current state of the form. The current user-submitted data is stored in $form_state->getValues(), though form validation functions are passed an explicit copy of the values for the sake of simplicity. Validation handlers can also use $form_state to pass information on to submit handlers. For example: $form_state->set('data_for_submission', $data); This technique is useful when validation requires file parsing, web service requests, or other expensive requests that should not be repeated in the submission step.

The current state of the form.

An associative array containing the structure of the form.

The current state of the form.

The unique string identifying the form.

An associative array containing the structure of the form.

The current state of the form.

The unique string identifying the form.

An associative array containing the structure of the form.

The current state of the form. The current user-submitted data is stored in $form_state->getValues(), though form validation functions are passed an explicit copy of the values for the sake of simplicity. Validation handlers can also $form_state to pass information on to submit handlers. For example: $form_state->set('data_for_submission', $data); This technique is useful when validation requires file parsing, web service requests, or other expensive requests that should not be repeated in the submission step.

A unique string identifying the form for validation, submission, theming, and hook_form_alter functions. Is only present on the initial call to the method, which receives the entire form array as the $element, and not on recursive calls.

An associative array containing the structure of the form.

The current state of the form. The current user-submitted data is stored in $form_state->getValues(), though form validation functions are passed an explicit copy of the values for the sake of simplicity. Validation handlers can also $form_state to pass information on to submit handlers. For example: $form_state->set('data_for_submission', $data); This technique is useful when validation requires file parsing, web service requests, or other expensive requests that should not be repeated in the submission step.

The current state of the form.