laravel-json-api/core v4.laravel-json-api/core v4 and v5.8.2.422.acceptsMiddleware functionality
when there is no matched route on the request.laravel-json-api/core and laravel-json-api/validation dependencies.Initial stable release, with no changes from 1.0.0-beta.4.
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.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.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.ExceptionParser now has the acceptsAll()
and acceptsMiddleware() helper methods, for determining whether JSON:API errors should be rendered.Initial beta release, no changes since alpha.2.
application/json using the parser's acceptsJson() method.accept() method.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.Initial release.
How can I help you explore Laravel packages today?