-
-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(4) ref(tracing): Extract UserInteractionTracing as standalone interaction #3999
Conversation
Co-authored-by: LucasZF <lucas-zimerman1@hotmail.com>
Android (legacy) Performance metrics 🚀
|
iOS (legacy) Performance metrics 🚀
|
iOS (new) Performance metrics 🚀
|
PR description says |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small note on the PR description, but nothing blocking the PR, LGTM!
Instructions and example for changelogPlease add an entry to Example: ## Unreleased
- Extract UserInteractionTracing as standalone interaction ([#3999](https://github.com/getsentry/sentry-react-native/pull/3999)) If none of the above apply, you can opt out of this check by adding |
📢 Type of change
📜 Description
This PR moved User Interaction Tracing to a standalone integration.
To do so this PR refactors part of ReactNativeTracing. Introducing ReactNative specific
startIdleSpan
andstartIdleNavigationSpan
. These function are used in both ReactNativeTracing and User Interaction Tracing integrations.Moving the tracking to a standalone integration will let us measure usage of this feature (enabled integrations telemetry).
This PR introduces user facing breaking change.
Before
After
💚 How did you test it?
sample app, tests
📝 Checklist
sendDefaultPII
is enabledPredecessor to this PR