Added

• #106 adds support for PHP 7.3.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

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

Fixed

• Nothing.

Added

• Nothing.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #105 fixes default behaviour when the configuration flagremove_empty_data
  is not set; in that scenario, data will not change as described in the
  documentation. This fixes a BC break introduced in version 1.7.0.

Added

• #102 adds the configuration flagremove_empty_data. If set and boolean
  true, it causes removal of empty key/value pairs from filtered input data.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• Nothing.

Added

• Nothing.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #99 fixes how theContentValidationListener chooses an input filter
  onDELETE requests. Starting in 1.6.0, it erroneously would fall back to the
  default input filter if noDELETE orDELETE_COLLECTION input filter was
  found. However, this was a backwards incompatible change from previous
  versions, which would not apply the default input filter forDELETE
  requests. As such, a new check was added to provide the previous behavior in
  such situations.

Added

• #98 adds support for specifying controller-specific input filters for
  DELETE requests, using the keysDELETE andDELETE_COLLECTION. The input
  filter associated with the key will be applied to the request body.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• Nothing.

Added

• #96 adds the ability to specify different input filters forcollections (versus
  entities). These may be indicated using<METHOD>_COLLECTION within your resource input filter configuration.

Changed

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• Nothing.

Added

• #95 adds support for PHP 7.1 and 7.2.

Changed

• #93 modifiesContentValidationListener::onRoute() to set the event parameter
  ZF\ContentValidation\ParameterData with the data it has aggregated prior to emitting the event
  ContentValidationListener::EVENT_BEFORE_VALIDATE. It also now pulls that parameter immediately
  prior to validating data, merging its value with the original data aggregated, and using the
  result when validating. This feature allows you to manipulate the data being validated prior
  to validation; one use case is to inject route matches into the data set to validate.

Deprecated

• Nothing.

Removed

• #95 removes support for HHVM.

Fixed

• Nothing.

Added

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #88 fixes an issue when handling PATCH requests in JSON formats that include a blank field name. Prior to the patch, these would raise a 400 error with a stack trace; with the fix, we now issue a 400 error with the message 'Unrecognized field ""'.

Added

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #83 fixes how input filters are processed when performing GET collections to REST endpoints. This ability was introduce in 1.3.0, but failed to take into account that query string arguments cannot properly represent multiple entities, which led to any input filter for aZF\Rest\Resource::fetchAll() operation to be invalid. The change introduced treats such input filters such that they do not operate as aCollectionInputFilter; as such, they should only be used to retrieve values that will be used to sort or filter the collection returned.
• #84 fixes how unknown fields are pulled fromCollectionInputFilter instances when reporting their presence for Problem Details. Previously, it would report only the index of the collection set, and not the values from each; with this release, it now reports the which sets had unknown values, along with the unexpected values detected.

Added

• Nothing.

Deprecated

• Nothing.

Removed

• Nothing.

Fixed

• #81 fixes an issue with how data was being returned from the content validation listener when raw data was to be used, and unknown fields allowed. In cases where the data was an indexed array (which happens with zf-apigility-admin when submitting an input filter to the API), the data and unknown values, which were identical, were being merged before return. Since raw data always contains all unknown values, we now return before merging.