Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Exceptions Laravel Package

laravel-json-api/exceptions

View on GitHub
Deep Wiki
Context7
3.3.0

Added

  • Package now supports Laravel 13.

Changed

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

Added

  • Package now supports Laravel 11 and 12.
3.1.0

Added

  • Allow laravel-json-api/core v4 and v5.

Fixed

  • Remove deprecation notices for PHP 8.4.
3.0.0

Changed

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

Added

  • Debug exception output now includes any previous exceptions.
2.0.1

Fixed

  • #3 Ensure HTTP status is correctly set when the status on a validation exception is not 422.
2.0.0

Changed

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

Fixed

  • laravel-json-api#204 Fixed acceptsMiddleware functionality when there is no matched route on the request.
1.1.0

Added

  • Package now supports Laravel 9.
  • Added support for PHP 8.1.
  • Package now supports v2 of the laravel-json-api/core and laravel-json-api/validation dependencies.
1.0.0

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

1.0.0-beta.4

Added

  • When converting an exception to the default JSON:API error, detailed exception information will now be added to the JSON:API error if the application is running in debug mode. The exception code will be added to the code member, and the actual exception message to the detail member. The meta member will contain the exception class, file, line number and stack trace.

Removed

  • This package no longer handles the UnexpectedDocumentException from the laravel-json-api/spec package. The exception has been removed from that package, and it instead throws a JsonApiException if it cannot decode a JSON string.
1.0.0-beta.3

Added

  • Multiple accept* helpers can now be added to the exception parser. This is useful when there are multiple different circumstances where you want to force the parser to render JSON:API errors - for example, if the client accepts JSON or if the current route has the api middleware. When multiple accept helpers are used, the parser will render JSON:API errors if any of the helpers return true.
1.0.0-beta.2

Added

  • #1 The ExceptionParser now has the acceptsAll() and acceptsMiddleware() helper methods, for determining whether JSON:API errors should be rendered.
1.0.0-beta.1

Initial beta release, no changes since alpha.2.

1.0.0-alpha.2

Added

  • Allow the exception parser to render responses for application/json using the parser's acceptsJson() method.
  • Allow a developer to provide a callback to determine if an exception should be rendered as JSON:API via the parser's accept() method.

Changed

  • BREAKING Made method signatures on the ExceptionParser class consistent, so that they now take the exception as the first argument and the request as the second. (Previously some had these the other way round.) This makes the signatures consistent with the order of arguments that Laravel uses when calling render callbacks.
1.0.0-alpha.1

Initial release.

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
mehedimi/laravel-amp-mail
happones/laravel-vue-i18n-generator
jwerd/inertia-table
siberfx/flysystem-wasabi
hollyit/token-replace
ippanelcom/laravel-sdk
adachsoft/changelog-linter
adachsoft/collection
payerurl/telegrambot-crypto-payment-instant-payout
dskripchenko/laravel-hybrid-search
riorizkyrainey/lara-ced
mehedimi/static-vel
zharp/zharp
nonsapiens/bigquery-model-sync
lgu-bayambang-ict-office/lgu-laravel-development-standards
andydefer/laravel-support
se7enxweb/flysystem
lampwick/laravel
jeslage/statamic-emojis
micahdshackelford/rmap-laravel