Skip to content

Commit cf368b1

Browse files
authored
meta: Backfill v9 migration guide items (#14459)
Backfills items to the draft migration guide for v9 that we missed - #14433 - #14454
1 parent 91a4985 commit cf368b1

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

docs/migration/draft-v9-migration-guide.md

+10-9
Original file line numberDiff line numberDiff line change
@@ -4,19 +4,20 @@
44

55
## General
66

7+
- **Returning `null` from `beforeSendSpan` span is deprecated.**
78
- **Passing `undefined` to `tracesSampleRate` / `tracesSampler` / `enableTracing` will be handled differently in v9**
89

9-
In v8, a setup like the following:
10+
In v8, a setup like the following:
1011

11-
```ts
12-
Sentry.init({
13-
tracesSampleRate: undefined,
14-
});
15-
```
12+
```ts
13+
Sentry.init({
14+
tracesSampleRate: undefined,
15+
});
16+
```
1617

17-
Will result in tracing being _enabled_, although no spans will be generated.
18-
In v9, we will streamline this behavior so that passing `undefined` will result in tracing being disabled, the same as not passing the option at all.
19-
If you are relying on `undefined` being passed in and having tracing enabled because of this, you should update your config to set e.g. `tracesSampleRate: 0` instead, which will also enable tracing in v9.
18+
Will result in tracing being _enabled_, although no spans will be generated.
19+
In v9, we will streamline this behavior so that passing `undefined` will result in tracing being disabled, the same as not passing the option at all.
20+
If you are relying on `undefined` being passed in and having tracing enabled because of this, you should update your config to set e.g. `tracesSampleRate: 0` instead, which will also enable tracing in v9.
2021

2122
## `@sentry/utils`
2223

0 commit comments

Comments
 (0)