- Drop Python 3.5 support
- Update documentation
- Fix bug with content negotiation
- Add cherry-picked and improved helpers from python-mimeparse
- Improve content negotiation (fix #185) with python-mimeparse
- Update requirements
- Fix bug with wrong query parameters of links in compound documents
- Fix
trafaret
requirement to 1.0.2 (includedrfc3339.Date
)
BREAKING CHANGES!
- Schema is separated into Schema (marshaller) and Controller
- Request context instantiated in handlers and was renamed to
JSONAPIContext
- Change signature of setup JSON API method in application (now we should pass a mapping between schemas and controllers)
- New abstract base class for Controller
- Schema and Controller must be initialized with only one parameter —
JSONAPIContext
- Passing a context to almost each method of Schema no more required (context is accessible from Schema or Controller instance directly)
- Remove decorator for JSON API handlers (content negotiation moved to middleware)
- Refactored fields and schema modules
- Improved fetching of compound documents
- Examples are updated to conform with all changes in this release
- Fix bug with no Accept header in request
- Improve content type negotiation
- Improve documentation
- Add field for Date
- Add example based on fantasy database
- Introduce JSON API integration test suite (not done yet!)
- Improve collections helpers
- No more links normalization by default
- Move meta object at top level of result document
- Constants, enums and structs refactoring (backward incompatible)
- Add useful typings
- Documentation fixes
- Extend development requirements
- Improve performance of URL resolving again. At this time with usage of standard Python urllib
- Upgrade requirements
- Improve performance of URL resolving in Link field (with cachetools)
- Upgrade requirements
- Documentation improvements
- Update README
- Upgrade requirements
- Simple example of usage is added
- Fix bug in handler of relationship query
- Fix bug with wrong read-only field error
- Don’t require setup ID field in Schema to update a resource
- Add multidict to requirements and to README
- Fix small bug with wrong empty sorting in RequestContext
- Add support for customizable inflection of fields from query string.
- Convert static methods of RequestContext to class methods
- Update docs of RequestContext methods
- Fix packaging of ABCs and compats
- Abstract base classes refactoring (separate Field and Schema ABCs)
- Fix bug with compound documents in case models has no property “resource_id”
- Remove buggy helper to check subclass of any instance
- Decompose setup application method to increase readability
- Properly error raised in jsonapi_handler decorator
- Use one field instead of two to check what type of relation have the field
- Properly use abstract base classes. Inherit SchemaABC from ABC.
- Rename resource validation methods (backward incompatible)
- Add Tuple field
- Fix bug with List field items enumeration
- Fix wrong conversion of Decimal field to string on deserialization
- Add yarl (>=0.13) to requirements
- Add support for length range specifying for List field
- Convert document render utility to async coroutine (backward incompatible)
- Rename Error class property "json" to "as_dict" to clarify
- Use MultiDict for request context filters and FilterRule tuple (backward incompatible)
- Debug info on request context creation
- Add support for nullable List field
- Fix bug with wrong exit from compound documents fetch utility ("return" instead of "break")
- Remove recursive fetching of compound documents. Replace it with simple loop.
- Fix bug with fetching compound documents when query parameter "include" contains the same relation twice and more.
- Fix bug with non-underscored relation name in relationship handlers
- Add support for field names conversion passed to "include" request context
- Update development requirements
- Avoid assertion in Registry ensure identifier method
- Make Schema getter of object id static
- Avoid to filter out empty fields of rendered documents (less memory and faster)
- Get id field of schema more safely in URI resource ID validator
- Add support for load only fields (like a Marshmallow)
- Asynchronous validators support
- Routes namespace can be customized
- Relative links support
- Improve serialization result default keys creation
- Refactor schema serializer to fix bug with no resource link in result
- Clean-up validation of expected ID in pre-validaiton of resource
- Use status property of ErrorList in error middleware to return HTTP status
- Remove default getter from Link field, because it doesn't used anymore
- Migrate to trafaret >= 0.11.0
- Fix requirement of trafaret to version greater than 0.11.0
- Properly handle missing values in deserialization and validation
- Add support for validation of Relationships ID field
- Normalize resource_id parameter usage in all mutation methods.
- Add fetch_resource schema coroutine to receive resource instance by ID.
- Add separate method for mapping deserialized data to schema.
- Context is required parameter for deserialization schema method.
- Move docs to ABC schema.
- Properly handle allow_none parameter for UUID field
- Fix arguments passed to validators
- Pass context to value setter in update methods
- Strict member names and type checking to conform JSON API requirements (routes and schema level). See also: http://jsonapi.org/format/#document-member-names
- Strict check for overrides of handlers
- Improve debug logging
- Initialize default relationships links in meta-class, to avoid bug with empty names of relationships fields
- Rename resource ID parameter of query_resource schema' method.
- Pagination is initialized from request by default. Remove separate class method of BasePagination to initialize pagination instance
- Improve value validation error for absent fields
- Improve validation error of string field with choices
- Customisable JSON API handlers support
- DRY in handlers
- Move context builder from middleware to jsonapi_handler decorator
- Request context receive optional resource_type now
- Revert back to asynchronous setters, because it's used in update relationships and it might want to query DB, for example
- Base Registry class from UserDict, so Registry is a dict with ensure_identifier method.
- More strict typing checks on setup.
- Fix bug with mutation not cloned resource in method for delete relationship
- Require JSON API content type on delete relationships
- Method for update return original and updated resource as result. Updated resource is created via deepcopy. It will be useful to determine returned HTTP status
- Fix bug with enumeration (choices) in String field
- Fix bug with context event setup for OPTIONS, HEAD and another request methods not used in JSON API
- Mass refactoring of schema, fields, validation and decorators
- Generic approach to setup Schema decorators is used (inspired by Marshmallow)
- Fields are used only for encode/decode now (with pre/post validation). Additional validators for fields must be created on schema level
- Custom JSON encoder with support JSONPointer serialization
- Remove boltons from requirements
- No more remap input data dictionary with key names to underscores conversion.
- Add helpers "first" and "make_sentinel" (cherry-picked from boltons)
- Fix enumeration (choices) support in String field
- Setup content-type validation on mutation API methods (application/vnd.api+json is required)
- Properly get and encode relationships fields
- Update docs and typing for ensure_identifier Registry's method
- Fix bugs related to Python 3.5
- Generation of documentation on RTD is fixed
- Python 3.5 compatibility changes
- Handle aiohttp-json-api exceptions and errors in middleware. If exceptions is not related to JSON API errors, then exception is reraised
- Huge refactoring of RequestContext
- No more use of boltons cachedproperties, instead use parsing static methods related to each request context' entity
- Update docs for RequestContext methods
- Add typings to RequestContext
- Properly handle error with wrong relation name (raise HTTP 400)
- Fix bdist_wheel python tag to support Python 3.5
- Python 3.5 support (avoid usage of Python 3.6 format strings)
- Registry is plain object now
- Custom Registry support (registry_class parameter in
aiohttp_json_api.setup_jsonapi
method) - Log debugging information at start about registered resources, methods and routes
- Use OrderedDict inside SchemaMeta
- Fix bug with JSONPointer when part passed via __truediv__ is integer
- Validate relationship object before adding relationship in ToMany field
- Fix bugs with validation of resource identifier in relationships fields
- Add typings for base fields
- Setup of JSON API must be imported from package directly
- Fix bugs with decode fields and allow None values
- Update HISTORY
- Fix bug with Enum choices of String field
- Return resource in update method of Schema class. This will be helpful in inherit classes of Schemas.
- Setup auto-deploy to PyPI in Travis CI
- Initial release on PyPI
- Improve documentation
- Don't use attrs package anymore
- Refactor requirements (move it into setup.py)
- Schema imports refactoring (e.g. don't use
aiohttp_json_api.schema.schema.Schema
anymore)
- Upgrade requirements
- Fix setup.py
- Add test for Decimal trafaret field
- Dirty initial version