Thanks @paksu! Could you also add this option to the docs? https://github.com/getsentry/raven-js/blob/master/docs/usage.rst

@getsentry/javascript should we delete this attribute before sending a payload to the server or will it just be skipped during processing in there?

Additional unhandled attributes show up as warnings/errors in the UI.

Let's get rid of it before sending the payload then @paksu.

My only concern with this solution, is that we're somewhat mixing options with data and I'm not sure if we should do this. On the other hand adding additional options argument is even worse. I'm +1 for either leaving "as is", or wrapping all "functionality related options" to be passed as {options: {}} attribute.

Hey @kamilogorek. I added documentation, refactored into into options object and cleaned the options from request payload. Does it look good now?

Looks good to me! What do you think about this solution @getsentry/javascript? It's a clear separation of data/options, which we can reuse in other js SDKs solutions.

Question: should we also have skipWhitelistsUrls and/or skipIgnoreErrors? (No.)

I feel like we should explore how this could be done more elegantly. I'd almost prefer an option like force: true bypass all checking altogether. At least that scales to be useful for more scenarios, both today and in the future.