Skip to content

Commit ac2e742

Browse files
Add type caveat for contexts (#3557)
Co-authored-by: Katie Byers <[email protected]>
1 parent 19e8299 commit ac2e742

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

src/platforms/common/enriching-events/context.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,9 @@ Then, use <PlatformIdentifier name="set-context" /> and give the context a uniqu
3636

3737
<PlatformContent includePath="enriching-events/set-context" />
3838

39-
There are no restrictions for naming contexts or their fields. However, there is a set of conventions for common contexts. For more information, refer to the [contexts interface developer documentation](https://develop.sentry.dev/sdk/event-payloads/contexts/).
39+
There are no restrictions on context name. In the context object, all keys are allowed except for `type`, which is used internally.
40+
41+
Learn more about conventions for common contexts in the [contexts interface developer documentation](https://develop.sentry.dev/sdk/event-payloads/contexts/).
4042

4143
## Size Limitations
4244

0 commit comments

Comments
 (0)