v2.5.0

This is a minor version release because the meaning of the scrubFields configuration option has changed slightly. If you upgrade without any changes we may end up scrubbing more fields than you had before. Please see the second bullet point below for how this has changed.

• The way we work with network requests for telemetry is a bit janky because of how XHR requests work and because we want to capture data without manual instrumentation. We do this via a monkey patch, this release changes a little bit of the semantics of that monkey patch to try to capture telemetry data in more cases. (#682)

• When you set the scrubFields configuration option, we have two choices, we either:

  • concat your supplied list to the default
  • overwrite the default with whatever you supply

  If we do the first then how do you remove things you don't want scrubbed but which are in the default list? If we do the second, how do you add all of the defaults without having to copypasta them from our code?

  This release introduces the configuration boolean overwriteScrubFields which will determine which of the above two behaviours we follow. By default we will concat the scrubFields in the configuration that you set with the default set of fields defined in our package.json. If you set overwriteScrubFields to true then we will instead use your scrubFields value by itself ignoring whatever is currently set.
  (#684)