mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-11-23 10:30:04 +01:00
703a063ad1
Attempts to send metrics would fail when no `options` were used. This
was because when the options parameter was not set, it was often sent
over our RPC connection as `undefined`, which gets serialized to `null`
when the message is converted to JSON. This `null` parameter didn't
trigger the default parameter set in the metametrics controller, as
default parameters are only used for `undefined`.
Instead the `options` parameter is now treated as fully optional, with
no default value set. The optional chaining operator is used to ensure
it won't blow up if it's not set. A fallback of `{}` was used for the
one destructure case as well.
|
||
|---|---|---|
| .. | ||
| account-import-strategies | ||
| controllers | ||
| lib | ||
| migrations | ||
| platforms | ||
| background.js | ||
| chromereload.js | ||
| contentscript.js | ||
| first-time-state.js | ||
| initSentry.js | ||
| inpage.js | ||
| metamask-controller.js | ||
| phishing-detect.js | ||
| runLockdown.js | ||
| ui.js | ||