-
-
Notifications
You must be signed in to change notification settings - Fork 357
(7) wip: Refactor Navigation Integrations to use new function style #4003
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: LucasZF <lucas-zimerman1@hotmail.com>
Contributor
Android (legacy) Performance metrics 🚀
|
Contributor
iOS (legacy) Performance metrics 🚀
|
Contributor
iOS (new) Performance metrics 🚀
|
Closed
lucas-zimerman
approved these changes
Aug 13, 2024
Collaborator
lucas-zimerman
left a comment
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.
Thank you for all the comments on the code! LGTM!
Base automatically changed from
kw/tracing-integrations-independent-order
to
v6
August 14, 2024 07:53
Collaborator
|
@krystofwoldrich we should add this to the migration guide to avoid issues like #4099 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📢 Type of change
📜 Description
This PR refactors
ReactNativeNavigationInstrumentationandReactNavigationInstrumentationproperties ofreactNativeTracingIntegrationto standalone integrations.This PR removes
RoutingInstrumentationinterface which is replaced bystartIdleNavigationSpan,getDefaultIdleNavigationSpanOptionsandgetCurrentReactNativeTracingIntegration().setCurrentRoute('new_route').React Navigation
React Navigation v4 support is removed. The integration supports v5 and newer.
React Native Navigation
Custom Navigation
💡 Motivation and Context
This change refactoring decouples React Native Tracing and the navigation integrations. Now each navigation integration is one standalone file which contains the navigation library specific code.
💚 How did you test it?
sample app, unit tests
📝 Checklist
sendDefaultPIIis enabled