zend-form 2.14.3

Added

• Nothing.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #235 fixes PHP 7.4 compatibility.

zend-form 2.14.2

Added

• Nothing.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #232 fixes validating $creationOption
  of Zend\Form\ElementFactory. Allowed values are: array, Traversable or null.
  If invalid value provided exception will be thrown.

• #234 registers Search and Tel form elements
  within Zend\Form\FormElementManager plugin manager.

zend-form 2.14.1

Added

• Nothing.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #230 fixes the "__clone method called on non-object" error that happens when
  the $targetElement is null within a Collection instance. It now properly
  sets the data to an empty array in such circumstances.

zend-form 2.14.0

Added

• #228 adds support for PHP 7.3.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• #228 removes support for zend-stdlib v2 releases.

Fixed

• Nothing.

zend-form 2.13.0

Added

• #224 adds support for zend-hydrator v3 releases, while keeping support for
  versions 1 and 2.

• #211 adds support for the HTML5 minlength attribute in all form elements
  that support it.

• #217 adds Zend\Form\View\HelperTrait, which can be used to provide IDE
  autocompletion for view helpers provided by zend-form. See
  https://docs.zendframework.com/zend-form/view-helpers/#ide-auto-completion-in-templates
  for more information.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• Nothing.

zend-form 2.12.1

Added

• Nothing.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #218 ensures object values of select elements can be rendered without error.

• #216 fixes an issue when performing data binding and a fieldset has no mapped
  input elements, casting null values to empty arrays to ensure they can be
  passed to an input filter.

• #207 fixes the return value annotation for the Fieldset::get() method to
  indicate it can also return a FieldsetInterface instance.

zend-form 2.12.0

Added

• #194 adds the ability to whitelist additional HTML attributes for use with a view helper,
  as well as attribute prefixes. These can be enabled via the following:

  $helper->addValidAttribute('attribute-name');
  $helper->addValidAttributePrefix('prefix-');

• #188 adds a new method to the FormElementErrors view helper, setTranslateMessages(bool $flag).
  By default, the helper continues to translate error messages (if a translator
  is present), as introduced in 2.11.0. However, using this method, you can
  disable translation, which may be necessary to prevent double translation
  and/or to reduce logs from missed translation lookups. Because the method
  implements a fluent interface, you may do so in one line:

  echo $this->formElementErrors()->setTranslateMessages(false)->render($element);

  Note: you will need to reset the value afterwards if you want translations to occur
  in later invocations.

Changed

• #193 modifies how attributes are escaped. If zend-espaper raises an exception
  for an invalid attribute value, helpers will now catch the exception, and use
  a blank value for the attribute. This prevents 500 errors from being raised
  for such pages.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• Nothing.

zend-form 2.11.0

Added

• #104 adds the ability for the FormElementErrors view helper to translate validation error messages using the composed translator and text domain instances.

• #171, #186, and #187 add support for PHP 7.2.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• #171 removes support for HHVM.

• #186 removes support for PHP 5.5.

Fixed

• #162 fixes an issue with hydration when a form has called setWrapElements(true), ensuring that binding values in a fieldset will correctly identify the elements in the provided data.

• #172 fixes the DateTime element such that it no longer attempts to use its DATETIME_FORMAT constant, but, rather, the value of the $format property, when representing the element; this change allows developers to override the format, which was the original intention.

• #178 loosens the checks in Zend\Form\Element\DateTime::getValue() to check against PHP's DateTimeInterface (vs DateTime) when retrieving the value; this fixes edge cases where it was instead returning the format for DateTimeImmutable values.

zend-form 2.10.2

Added

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #161 adds an import statement to the ElementFactory, fixing an error whereby checks for Traversable creation options would lead to a service creation exception; these now correctly identify traversable options and convert them to an array.
• #164 fixes how the FormElementManagerFactory factory initializes the plugin manager instance, ensuring it is injecting the relevant configuration from the config service and thus seeding it with configured form/form element services. This means that the form_elements configuration will now be honored in non-zend-mvc contexts.
• #159 fixes the behavior of the min and max attributes of the various DateTime elements, ensuring that the elements raise an exception during instantiation if the values provided are in a format that DateTime does not recognize for the element type in question.

zend-form 2.10.1

Added

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #134 fixes how the FormElementManager handles invokable classes when the autoAddInvokableClass flag is enabled. Previously, it used the built-in utilities from zend-servicemanager, but now correctly uses its own setInvokableClass() method, which forces usage of the ElementFactory for such classes, and thus ensures the name and options are passed to the element constructor.
• #136 fixes how error messages are provided when an element uses a required ArrayInput, but no values are submitted. Previously, no messages were returned; now they are.
• #156 fixes how elements that act as InputProviders are merged into parent CollectionInputFilters; previously, forms did not check if the element was in the target input filter composed in a CollectionInputFilter, leading to duplicate elements with varying behavior; now the inputs are correctly merged.