Skip to content

Commit

Permalink
docs: Update upgrading guide with top-level metadata
Browse files Browse the repository at this point in the history
  • Loading branch information
bengourley committed Mar 30, 2020
1 parent 526c897 commit d0f3bb8
Showing 1 changed file with 9 additions and 0 deletions.
9 changes: 9 additions & 0 deletions UPGRADING.md
Original file line number Diff line number Diff line change
Expand Up @@ -235,6 +235,15 @@ It remains possible to supply initial metadata in configuration:
})
```

All metadata is now required to have a section. If you were previously supplying metadata without a section name (this would display on your dashboard under the "Custom" tab), we have enabled passing `null` as the section name for continuity:

```js
- bugsnagClient.metaData.assetUrl = config.assetUrl
+ Bugsnag.addMetadata(null, 'assetUrl', config.assetUrl)
```

You should only use this method if you have a custom filter based on some top-level metadata, otherwise you should supply a section name for your metadata.

#### Context

On the client, context is now managed via `get/setContext()`:
Expand Down

0 comments on commit d0f3bb8

Please sign in to comment.