Expected behavior
When something like SOAP or xml is posted to laravel and an exception occurs I would expect to see that in the bugsnag interface under params.
Observed behavior
When something like SOAP or xml is posted to laravel and an exception occurs params is an empty array.
Steps to reproduce
Post XML data to a route and throw an exception note that the request in bugsnag is empty.
Version
Bugsnag: 3.10
Bugsnag Laravel: 2.11.1
Would something like a "raw" metadata addition be something that could be populated by getContent() rather than just relying on input() to get the post data?
Expected behavior
When something like SOAP or xml is posted to laravel and an exception occurs I would expect to see that in the bugsnag interface under params.
Observed behavior
When something like SOAP or xml is posted to laravel and an exception occurs params is an empty array.
Steps to reproduce
Post XML data to a route and throw an exception note that the request in bugsnag is empty.
Version
Bugsnag: 3.10
Bugsnag Laravel: 2.11.1
Would something like a "raw" metadata addition be something that could be populated by
getContent()rather than just relying oninput()to get the post data?