Messages include context as JSON string

[tremby]

When I look at the submitted issues in the Sentry interface, they all have a JSON-encoded representation of the context data after the message, such as test warning {"user":{"id":1,"email":"test@example.com"}} []. This particular issue was logged with \Log::warning('test warning');, with context added via a processor. I get the same result if instead of the processor I add the context data as you do in the example in the readme.

If I look at the JSON submitted to Sentry I see that this JSON-encoded context data is present in the message string. It seems to me this should not be there.

[tremby]

It turns out the fix is simple -- it's just a matter of removing %context% %extra% from the format string in AbstractServiceProvider line 42. I could provide this as a pull request if you like? Or is this by design? If so, why?

[pulkitjalan]

This was originally copied from sentry ravens own example (before getsentry/sentry-laravel), but context and extra are added via the RavenHandler in monolog so its not required here. Removed it now and tagged a new release.

Thanks