Skip to content
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.

Releases: zfcampus/zf-content-validation

zf-content-validation 1.8.0

05 Mar 17:20
Compare
Choose a tag to compare

Added

  • #106 adds support for PHP 7.3.

Changed

  • Nothing.

Deprecated

  • Nothing.

Removed

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

Fixed

  • Nothing.

zf-content-validation 1.7.1

05 Mar 17:16
Compare
Choose a tag to compare

Added

  • Nothing.

Changed

  • Nothing.

Deprecated

  • Nothing.

Removed

  • Nothing.

Fixed

  • #105 fixes default behaviour when the configuration flag remove_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.

zf-content-validation 1.7.0

26 Feb 20:09
Compare
Choose a tag to compare

Added

  • #102 adds the configuration flag remove_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.

zf-content-validation 1.6.1

13 Aug 20:59
Compare
Choose a tag to compare

Added

  • Nothing.

Changed

  • Nothing.

Deprecated

  • Nothing.

Removed

  • Nothing.

Fixed

  • #99 fixes how the ContentValidationListener chooses an input filter
    on DELETE requests. Starting in 1.6.0, it erroneously would fall back to the
    default input filter if no DELETE or DELETE_COLLECTION input filter was
    found. However, this was a backwards incompatible change from previous
    versions, which would not apply the default input filter for DELETE
    requests. As such, a new check was added to provide the previous behavior in
    such situations.

zf-content-validation 1.6.0

02 Aug 14:52
Compare
Choose a tag to compare

Added

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

Changed

  • Nothing.

Deprecated

  • Nothing.

Removed

  • Nothing.

Fixed

  • Nothing.

zf-content-validation 1.5.0

29 May 19:56
Compare
Choose a tag to compare

Added

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

Changed

  • Nothing.

Deprecated

  • Nothing.

Removed

  • Nothing.

Fixed

  • Nothing.

zf-content-validation 1.4.0

07 May 20:38
Compare
Choose a tag to compare

Added

  • #95 adds support for PHP 7.1 and 7.2.

Changed

  • #93 modifies ContentValidationListener::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.

zf-content-validation 1.3.6

06 Nov 17:21
Compare
Choose a tag to compare

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 ""'.

zf-content-validation 1.3.5

18 Aug 20:36
Compare
Choose a tag to compare

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 a ZF\Rest\Resource::fetchAll() operation to be invalid. The change introduced treats such input filters such that they do not operate as a CollectionInputFilter; 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 from CollectionInputFilter 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.

zf-content-validation 1.3.4

04 Aug 22:30
Compare
Choose a tag to compare

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.