getsentry / getsentry/sentry-dotnet
DataCollection phase 5: remove SendDefaultPii (next major)
- Dominant language
- C#
- Stars
- 770
- Forks
- 248
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 51
Description
Part of getsentry/sentry-dotnet#5420. Phase 5 — next major.
Remove `SendDefaultPii` and make the spec defaults unconditional:
* Remove `SentryOptions.SendDefaultPii`, `BindableSentryOptions.SendDefaultPii`, the Serilog `sendDefaultPii` sink parameter, and the legacy bridge in the resolver.
* Permissive spec defaults apply to everyone; migration guide entry for users who relied on `SendDefaultPii = false` (point at the restrictive `DataCollection` block).
* Simplify native propagation (map from resolved config only).
* JS analogue: v11 cleanup, [getsentry/sentry-javascript#22056]().
Contributor guide
Research direction
Locate SentryOptions.SendDefaultPii, BindableSentryOptions.SendDefaultPii, the Serilog sendDefaultPii parameter, and the resolver's legacy bridge. Read the resolved DataCollection handling and native propagation first, then find the migration guide and existing tests. Done means the option and bridge are removed, restrictive DataCollection guidance is documented, native propagation uses resolved config, and affected tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- developer-experience, documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100