Skip to content

Latest commit

 

History

History
91 lines (53 loc) · 2.75 KB

CHANGELOG.md

File metadata and controls

91 lines (53 loc) · 2.75 KB
Raw

CHANGELOG

0.5.0

  • Support for Zend\Stdlib 2.7 and Zend\Hydrator

0.4.5

  • Remove automatic 304 Etag as it causes a lot more problems as it solves

0.4.4

  • ResourceResponseListener only modifies response if it is a ResourceViewModel

0.4.3

  • isRootTemplate now work even if you have called the renderResource helper inside a view

0.4.2

  • Does not modify status code response if an exception is contained into the MvcEvent

0.4.1

  • Make sure validation does not fail be setting an empty value if no body is present in the request

0.4.0

  • Complete rewrite of ZfrRest. All the concepts have been changed in favour of an explicit module, please read the new docs.
  • PHP dependency has been raised to PHP 5.5

0.3.4

  • ZfrRest now supports coalesce filtering for "hasMany" or "findMany" requests type through the new, optional enable_coalesce_filtering module option. If enabled, ZfrRest will be able to respond to queries like /customers?ids[]=5&ids[]=64, where ids is a configurable primary key name.
  • Fix a bug with entry points. Previously, if you had an entry point configured as "/users", ZfrRest used to match URLs like "/userssssss".

0.3.3

  • Fix an issue with camelCased associations when rendering a resource

0.3.2

  • Added support for OneToOne association (assuming you have a "User" entity with a OneToOne association to a "Card" entity, you can now do a POST request like "/users/4/card")

0.3.1

  • ZfrRest now returns input errors correctly if no data was given in the body

0.3.0

  • Association mapping can now accept one new property: collectionController. It allows to map a specific association resource to a specific controller, instead of using the target entity mapping.
  • Add a doc section about optimizing ZfrRest for performance
  • Nested input filters are now supported when errors occur on POST on PUT

0.2.3

  • Associations can now have an extraction strategy set to PASS_THRU. This allows a parent hydrator to manually renders an association, and let the renderers reuse this result for the given association.
  • paginatorWrapper controller plugin now supports the resource data to be a plain PHP array.

0.2.2

  • routable metadata is now correctly taken into account by the router, so it won't route to the associated resource if the parameter is set to false.

0.2.1

  • HttpExceptionListener now stops propagation if it can handle a specific exception.

0.2.0

  • [FEATURE] You can now override the getInputFilter method in your controllers so that you can specify custom logic like setting validation groups depending on authorization, HTTP method...

0.1.0

  • Complete refactor, initial release (code cleaning, documentation...)

0.0.2

  • Exclude request base path from path

0.0.1

  • First release