You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ref(core)!: Remove Scope type interface in favor of using Scope class (#14721)
In v8, types have been exported from `@sentry/types`, while
implementations have been exported from other classes.
This lead to some duplication, where we had to keep an interface in
`@sentry/types`, while the implementation mirroring that interface was
kept e.g. in `@sentry/core`.
Since in v9 the types have been merged into `@sentry/core`, we can get
rid of some of this duplication. This means that certain things that
used to be a separate interface, will not expect an actual instance of
the class/concrete implementation. This should not affect most users,
unless you relied on passing things with a similar shape to internal
methods.
This PR removes the `Scope` interface, in favor of just using the scope
class everywhere.
This is related to
#9840
---------
Co-authored-by: Sigrid Huemer <[email protected]>
Let us know if this is causing issues in your setup by opening an issue on GitHub.
107
107
108
+
## 6. Type Changes
109
+
110
+
In v8, types have been exported from `@sentry/types`, while implementations have been exported from other classes.
111
+
This led to some duplication, where we had to keep an interface in `@sentry/types`, while the implementation mirroring that interface was kept e.g. in `@sentry/core`.
112
+
Since v9, the types have been merged into `@sentry/core`, which removed some of this duplication. This means that certain things that used to be a separate interface, will not expect an actual instance of the class/concrete implementation. This should not affect most users, unless you relied on passing things with a similar shape to internal methods. The following types are affected:
113
+
114
+
-`Scope` now always expects the `Scope` class
115
+
108
116
# No Version Support Timeline
109
117
110
118
Version support timelines are stressful for anybody using the SDK, so we won't be defining one.
0 commit comments