laravel-json-api/spec

Added

• Package now supports Laravel 13.

Changed

• Dropped support for laravel-json-api/core v4.

Added

• Package now supports Laravel 11 and 12.

Added

• Package now requires laravel-json-api/core v4 or v5.

Fixed

• Removed deprecation notices in PHP 8.4.

Changed

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

Fix translation keys in PT-BR translation files.

Fixed

• #7 Fix translation keys in the PT-BR translation file.

Changed

• Upgraded to Laravel 10 and set minimum PHP version to 8.1.

Add Spanish and Brazilian Portuguese translations.

Added

• #6 Added Spanish and Brazilian Portuguese translations.

Fixed

• The package now accepts "0" as a valid client generated id. Previously it was rejected with a message that the id could not be empty.
• The package now accepts a document for a resource with an expected id of "0". Previously the package did not recognise zero as an expected id.

Laravel 9 and add Italian translations.

Added

• Package now supports Laravel 9.
• Package now supports 2.0 of the laravel-json-api/core dependency.
• #5 Add Italian translation files.

Initial stable release.

Initial stable release, with no changes from 1.0.0-beta.2.

Changed

• BREAKING JSON decoding has been moved to a JsonDecoder class. This now throws a JsonApiException with translated error objects. Previously it threw the UnexpectedDocumentException class.
• BREAKING Document builder classes now expect the JsonDecoder as their first constructor argument. This is unlikely to affect consuming applications as the builder classes should be created via the service container.

Removed

• BREAKING Removed the UnexpectedDocumentException class as it is no longer in use.

Initial beta release, no changes since alpha.4.

Added

• Decoding JSON document now rejects an empty string with a specific exception message indicating that JSON is expected.
• Sending an incorrect resource type for a relationship is now rejected. For example, if a relation expects tags but the client provides posts, it will be rejected with a message that posts are not supported.

Changed

• BREAKING The ToOne, ToMany and Identifier value objects now expect the relation object to be passed into their constructor. This also affects the methods on the factory to create them.

Added

• Added French translations for error messages.
• If a to-many relation is sent for a to-one field (and vice versa), the value will be rejected with a new message that clearly indicates that the relation type is invalid.

Changed

• BREAKING The constructor for the to-many and to-one values now expect the relation name to be provided. This also means the factory create methods for these values has been updated to expect the relation name.

Bugfix

• #1 Add missing package discovery configuration to the composer.json.

Initial release.