Commit 3184ed2

committed

chore: Update upgrade guide

1 parent 0c75dce commit 3184ed2Copy full SHA for 3184ed2

File tree

-0

lines changed

-0

lines changed

Lines changed: 7 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -237,6 +237,13 @@ It remains possible to supply initial metadata in configuration:`
`237`	`237`	`})`
`238`	`238`	```
`239`	`239`
	`240`	+Previously, it was possible to add "top-level" metadata, i.e. data that you did not provide a specific `section` name for. In the dashboard, this would display under a tab with the heading "Custom". Since a section name is now required, for continuity both visually and for any custom filters you may have set up based on such data, you should set the section name to `'custom'`:
	`241`	`+`
	`242`	+```diff
	`243`	`+- bugsnagClient.metaData = { processId: 'aa874cbd', role: 'image-resizer' }`
	`244`	`++ Bugsnag.addMetadata('custom', { processId: 'aa874cbd', role: 'image-resizer' })`
	`245`	+```
	`246`	`+`
`240`	`247`	`#### Context`
`241`	`248`
`242`	`249`	On the client, context is now managed via `get/setContext()`:

Comments

(0)