message: Add comment on req vs request naming, http interface, convenience, etc
diff: @@ -228,6 +228,14 @@ extend(Raven.prototype, {
  values: domainContext.breadcrumbs || this._globalContext.breadcrumbs || []
  };
  + /*
  + `request` is our specified property name for the http interface: https://docs.sentry.io/clientdev/interfaces/http/
  + `req` is the conventional name for a request object in node/express/etc
  + we want to enable someone to pass a `request` property to kwargs according to http interface
  + but also want to provide convenience for passing a req object and having us parse it out
  + so we only parse a `req` property if the `request` property is absent/empty (and hence we won't clobber)
  + parseUser returns a partial kwargs object with a `request` property and possibly a `user` property
  + */
  kwargs.request = extend({}, this._globalContext.request, domainContext.request, kwargs.request);
  if (Object.keys(kwargs.request).length === 0) {
  var req = extend({}, this._globalContext.req, domainContext.req, kwargs.req);
  