Commit d0f3bb8

committed

docs: Update upgrading guide with top-level metadata

1 parent 526c897 commit d0f3bb8Copy full SHA for d0f3bb8

File tree

-0

lines changed

-0

lines changed

Lines changed: 9 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -235,6 +235,15 @@ It remains possible to supply initial metadata in configuration:`
`235`	`235`	`})`
`236`	`236`	```
`237`	`237`
	`238`	+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:
	`239`	`+`
	`240`	+```js
	`241`	`+- bugsnagClient.metaData.assetUrl = config.assetUrl`
	`242`	`++ Bugsnag.addMetadata(null, 'assetUrl', config.assetUrl)`
	`243`	+```
	`244`	`+`
	`245`	`+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.`
	`246`	`+`
`238`	`247`	`#### Context`
`239`	`248`
`240`	`249`	On the client, context is now managed via `get/setContext()`:

Comments

(0)