Releases: digitalsadhu/loopback-component-jsonapi
New configurability options
New features:
- attributes whitelisting
- serialization hooks
- custom serialization on a model by model basis
See README.md for more details
New configurability options
- Adds ability to exclude models and methods from being json api serialized/deserialized
- Adds ability to disable the default behaviour of hiding various methods not relevant to jsonapi spec from the api
Include filter
This release supports side loading via 'include'
Example:
GET /api/posts/9/?include=author
The author for post 9 will be included as part of the document.
Create and update of relationship linkages
Description
This is a bit of milestone release!
Thanks to @BenjaminHorn via #73 we now support create/update/delete of relationship linkages during the create and update of a resource. With this feature addition, we now provide enough functionality to be useful for an ember js developer.
The only feature we need to land to make life better for ember developers is side loading data which is currently in the works.
It's also worth noting that we now have 100 passing integration tests so I feel like we have a fairly solid solution and am happy to change our 'alpha' label to a 'beta' label. We welcome feedback and especially bug reports so we can fix anything ahead of a 1.0 release.
Readme improvements, caseify feature removal
Description
This release gets a minor bump because we have removed the ability to configure type, attribute and relationship key cases. The implementation had introduced bugs and you can configure case however you'd like in your loopback models so it wasn't necessary.
Whats included in this release:
- removal of case options
- improvement to readme.md documentation
- additional tests
- editorconfig file added to project
Bug fixes
Fixes a bug where relationship objects were pointing at themselves in certain cases.
Bug fixes
Fixes issue where self links in a collection were always pointing to id 1.
Error handler improvements, relationship improvements
Breaking changes:
- Changes to the way error codes are returned. Status is general eg. 400 or 500 and error objects are more specific. Eg. 404
Non breaking changes:
- Code cleanup
- Relationship improvements
Bug fixes/refactoring
Adds some support for hasOne relationship.
Fixes 406 Accept header issue.
Major serializer/deserializer refactor.
Consider this a breaking change as the relationships API surface has changed slightly
Adds bug fixes and tests
- Test for remote methods added and fixes added to get them working again
- Code quality improvements (eslint now running before tests) Files fixed to eslint definition