Returning a JsonResponse for respondWithNoContent() which makes it consistent with other response types.

The respondWithNoContent method should return a JsonResponse as well.…

… (instead of a standard Http response)

Error response trait

Error responses have been separated from the base controller and moved into a trait. This allows them to be used in the global error handler or in middleware.

This change does introduce a minor backwards compatibility break. If you were using errorArray please note that it can now take a second argument which is the status code. Previously it had 422 hardcoded as the status it would return. The idea was that this method would mock the validation response from Laravel but this made it very inflexible.

Fixing a bug with eager loads and hasOne/belongsTo relationships

0.7.2

Merge branch 'master' of github.com:navjobs/transmit

Fixing test coverage.

Adding test coverage for returning an item or collection without a re…

…source key.

Removing gateways

0.7.0

Updating Readme.

Removing an unneeded type hint.

0.6.1

Remove the typehint.

Improving Pagination

0.6

Making pagination more efficient.

Removing error codes and adding custom error response.

0.5

Adding a custom error response.

0.4.1: Merge pull request #2 from navjobs/feature/add-field-error

Adds errorArray() method.

0.4.0

Merge branch 'master' of https://github.com/NavJobs/laravel-api