v5.0.2

Upgrading

composer up laravel-json-api/laravel

What's Changed

• fix: authorizer response should be honoured on destroy action when no request class for resource by @haddowg in #302

Full Changelog: v5.0.1...v5.0.2

v5.0.1

Upgrading

composer up laravel-json-api/laravel

What's Changed

• fix: authorizer response with status should be honoured when unauthenticated by @haddowg in #301

Full Changelog: v5.0.0...v5.0.1

v5.0.0

Upgrading

composer require laravel-json-api/laravel --no-update
composer require laravel-json-api/testing --dev --no-update
composer up "laravel-json-api/*" cloudcreativity/json-api-testing

Although this is a major release with a breaking change (see below), the vast majority of applications should be able to upgrade without making any changes. You will only need to make a change if you're directly calling the authorizeResource() method on a JSON:API HTTP request class.

What's Changed

• feat: support Illuminate\Auth\Access\Response from authorizer by @haddowg in #298
• #70 The authorizer implementation now allows methods to return either bool or an Illuminate Auth Response.
• BREAKING The return type for the authorizeResource() method on both resource and query request classes has changed to bool|Response (where response is the Illuminate Auth response). If you are manually calling this method and relying on the return value being a boolean, this change is breaking. However, the vast majority of applications should be able to upgrade without any changes.

New Contributors

• @haddowg made their first contribution in #298

Full Changelog: v4.1.1...v5.0.0

v4.1.1

Upgrading

composer require laravel-json-api/laravel --no-update
composer require laravel-json-api/testing --dev --no-update
composer up "laravel-json-api/*" "cloudcreativity/json-api-testing"

What's Changed

• Update README.md 404 link correction by @SerhiiKotelnikov in #297
• Fix: remove deprecation notices in PHP 8.4 by @lindyhopchris in #300

New Contributors

• @SerhiiKotelnikov made their first contribution in #297

Full Changelog: v4.1.0...v4.1.1

v4.1.0

Upgrading

composer require laravel-json-api/laravel --no-update
composer up "laravel-json-api/*"

Changelog

Fixed

• core#17 Fix incorrect self link in related resource responses, and remove related link that should not exist. This has been incorrect for some time, but is definitely what the spec defines here.
• eloquent#36 Support Eloquent dynamic relationships.

Full Changelog: v4.0.0...v4.1.0

v4.0.0 - Laravel 11

Upgrading

composer require laravel-json-api/laravel:^4.0 --no-update
composer require laravel-json-api/testing:^3.0 --dev --no-update
composer up "cloudcreativity/*" "laravel-json-api/*"

What's Changed

• Feature: upgrade to Laravel 11 and drop PHP 8.1 by @lindyhopchris in #267

Changelog

Changed

• Package is now licensed under the MIT License.
• BREAKING Package now requires Laravel 11.
• Minimum PHP version is now 8.2.

Full Changelog: v3.4.0...v4.0.0

v3.4.0

Upgrading

composer require laravel-json-api/laravel --no-update
composer up "laravel-json-api/*"

What's Changed

• feat: add support to replace model in resource stub by @RobChatloop in #272

New Contributors

• @RobChatloop made their first contribution in #272

Full Changelog: v3.3.0...v3.4.0

v3.3.0

Upgrading

composer require laravel-json-api/laravel --no-update
composer up "laravel-json-api/*"

What's Changed

• Feature: allow middleware registration per action on resource and relations by @lindyhopchris in #268

Full Changelog: v3.2.0...v3.3.0

Route registration and exception improvements

Upgrading

composer require laravel-json-api/laravel --no-update
composer up "laravel-json-api/*"

Changelog

Added

• Exceptions converted to JSON:API errors when debug mode is on now include all previous exceptions.

Changed

• Registering routes no longer results in the server instance being thread-cached. This more accurately reflects
  production environments, where routes would be cached so there would be no thread-cached JSON:API server when handling
  a HTTP request. This means tests (and development environments where routes are not cached) more accurately behave in
  the same way as production environments.
• Exceptions thrown during the encoding process are no longer caught and re-thrown as previous exceptions. This is due
  to the number of questions we receive from developers who do not check previous exceptions, despite exception messages
  stating that there is a previous exception to look at.

ULID helper method on ID field

Upgrading

composer require laravel-json-api/laravel --no-update
composer up "laravel-json-api/*"

Changelog

Added

• core#12 Add ulid() method to the ID field class.