-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhance Error Reporting #794
Comments
Hmm, yes. The exception you're actually interested in is nested within the |
Actually scratch that, it turns out all you have to do is add this to the exception itself: public function getInnerException(): ?Throwable
{
return $this->originalException;
} That's going through testing now... |
This should work much better in https://github.com/flat3/lodata/releases/tag/v5.33.1 |
@27pchrisl |
Hi @27pchrisl,
In the meantime I have a small service running with your exceptional lodata package and so far everything is fine. Thank you for this great piece of software!
One thing that could be enhanced is the error reporting. The stacktrace for actual errors is not really helpful. This is one taken from my production environment.
Since this error arose from a real world user, I can find no clue, where the error happens from reading the log file alone. I can second guess from the feeback I got from users. But that directs me into a wider area than maybe neccessary.
Anyway, in a prefect world I would see in the log file the odata request URI or if it is a
$batch
request the individual request URI that led to the issue. With that additional information I could immediately understand where to look at and things would work out much easier in fixing issues that arise in production mode.The text was updated successfully, but these errors were encountered: