Comments (2)
I guess the trace contains too much data to pass through json_encode()
in a nice way.
There's two workarounds I can think of:
- skip the trace:
$options = ['includeExceptionTrace' => false];
$document = ErrorsDocument::fromException($exception, $options);
This completely ignores the trace and thus prevents this issue. However, you won't see any trace in the response.
- filter the output and pass it as new input to
sendResponse()
:
// get the data which would be send as response
$responseArray = $document->toArray();
// filter out what you don't want
foreach ($responseArray['errors'] as &$error) {
if (isset($error['meta']['trace']) === false) {
continue;
}
foreach ($error['meta']['trace'] as &$trace) {
if (isset($trace['args']) === false) {
continue;
}
foreach ($trace['args'] as $index => &$argument) {
if ($argument instanceof Laravel\Lumen\Application) {
unset($trace['args'][$index]);
}
}
}
}
// convert array to json
$options = ['array' => $responseArray];
$responseJson = $document->toJson($options);
// pass custom json to send as response
$options = ['json' => $responseJson];
$document->sendResponse($options);
Obviously, this is more cumbersome and less performant.
from jsonapi.
Well, looking better, I found that the problem occurs when trying to turn exceptions into a json.
This line on Document file. into toJson method.
This occurs because the trace has a Laravel\Lumen\Application instance.
Like can be see it below:
I don't know why or how fix this.
Somebody can help me?
from jsonapi.
Related Issues (20)
- Sync links with the latest spec
- Possibility to remove the automated self-link
- Allow to mask internal server errors as 503 status HOT 1
- Dependency Injection (using pimple )
- Keep 'relationships' and 'meta' for included resources
- add_relation in resource.php overwrite (array relations) HOT 2
- check key primary_links['self']['href'] HOT 6
- JSONP HOT 3
- Support v1.1 of the specification
- Parse request options: sparse fields, sorting, pagination, filtering HOT 4
- Problem with Content-Type: application/vnd.api+json HOT 3
- Spec 1.1 RC 2: add support for Local Ids HOT 1
- Spec 1.1 RC 2: make it easy to add describedBy links at root level HOT 1
- Spec 1.1 RC 2/3: add support for new properties of the link object HOT 1
- Spec 1.1 RC 2: support extensions and improve support for profiles HOT 1
- Validation for received document structure
- Validation for query parameters (include, sparse fieldset, sort, page, filter)
- Allow include in included and data resourses with same id
- Problems using ResourceDocument::fromObject
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jsonapi.