Plone-jsonapi-routes

------------------

**Changes**

- Handle catalog queries for multiple contents, which might be located in
different catalogs.
- Fixed an issue where the batch navigation did not show more results when using
multiple `portal_type` request parameters.

------------------

**Changes**

- Handle Reference Fields: Reference fields containing a reference can be
updated with a dictionary, e.g.::

{
uid: <UID of a content containing a reference field>,
ReferenceField: {
"title": "New Title"
}
}

- Added module `underscore` to the tests suite
- Validation for the entire object added
- Get the catalog to query from Archtype Tool and default to `portal_catalog`
- Use explicit namespace in route providers
- Handle Reference Fields (Fields containing and `ImplicitAcquisitionWrapper` object)
- Added ZCML directive to enable/disable route registrations (default enabled)::

<!-- Disable route registration -->
<plone:jsonapi
register_api_routes="False"
/>

- Version route is now part of the standard route providers
- Dropped AdvancedQuery handling

------------------

------------------

**CLOSED ISSUES**

- https://github.com/collective/plone.jsonapi.routes/issues/59: API URL for non standard content types
- https://github.com/collective/plone.jsonapi.routes/issues/60: Add a namespace to the route registrations
- https://github.com/collective/plone.jsonapi.routes/issues/63: handle richtext fields
- https://github.com/collective/plone.jsonapi.routes/issues/82: Plone 5 CSFR Protection
- https://github.com/collective/plone.jsonapi.routes/issues/80: Tests for Plone 5
- https://github.com/collective/plone.jsonapi.routes/issues/77: Problem with creating files
- https://github.com/collective/plone.jsonapi.routes/issues/62: 'reference_catalog' not found
- https://github.com/collective/plone.jsonapi.routes/pull/75: Fix api invocation on the zope root
- https://github.com/collective/plone.jsonapi.routes/pull/74: Reuse and improve code to check if a parameter in the request has a True value
- https://github.com/collective/plone.jsonapi.routes/pull/73: Using specifiers to format string (helps compatibility with Python 2.6, improves code readability)

------------------

**CLOSED ISSUES**

- https://github.com/collective/plone.jsonapi.routes/pull/66: api routes: sharing (docs)
- https://github.com/collective/plone.jsonapi.routes/pull/65: api routes: sharing (code)
- https://github.com/collective/plone.jsonapi.routes/pull/61: Use IConstrainTypes adapters for dexterity content

**API CHANGES**

- Sharing information can be displayed for objects. Use `?sharing=yes`

------------------

**CLOSED ISSUES**

- https://github.com/collective/plone.jsonapi.routes/issues/58: Unit tests: add tests for adapter module
- https://github.com/collective/plone.jsonapi.routes/issues/57: API Change: workflow data optional
- https://github.com/collective/plone.jsonapi.routes/issues/54: Let complete flag overrule "uid rule"
- https://github.com/collective/plone.jsonapi.routes/issues/53: Unit tests: add tests for api module

**API CHANGES**

- File data **not** included by default anymore. Use `?filedata=yes`

- Workflow data **not** included by default anymore. Use `?workflow=yes`

- Workflow data is now located at the key `workflow`

- The complete flag can be now negated, even if the full object is displayes `?complete=no`

- The `state` key is removed -- use `review_state` instead

- Parent URL data included now for brain results