Skip to content
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

feat(react): Add reactRouterV6BrowserTracingIntegration for react router v6 & v6.4 #10491

Merged
merged 3 commits into from Feb 5, 2024

Conversation

mydea
Copy link
Member

@mydea mydea commented Feb 5, 2024

feat(react): Add browserTracingIntegrations for router v4 & v5

This adds a new reactRouterV6BrowserTracingIntegration() exports deprecating the old routing instrumentation.

I opted to leave as much as possible as-is for now, except for streamlining the attributes/tags we use for the instrumentation.

I also updated the E2E tests to the new format.

@mydea mydea self-assigned this Feb 5, 2024
reactRouterV6Instrumentation,
browserTracingReactRouterV6Integration,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as in #10489, I think it would be cleaner to call it reactRouterV6BrowserTracingIntegration.

feat(react): Add browserTracingIntegrations for router v4 & v5

This adds a new `browserTracingReactRouterV6Integration()` exports deprecating the old routing instrumentation.

I opted to leave as much as possible as-is for now, except for streamlining the attributes/tags we use for the instrumentation.
@mydea mydea marked this pull request as ready for review February 5, 2024 12:56
@mydea mydea changed the title feat(react): Add browserTracingIntegration for react router v6 & v6.4 feat(react): Add reactRouterV6BrowserTracingIntegration for react router v6 & v6.4 Feb 5, 2024
@mydea mydea merged commit e4806d1 into develop Feb 5, 2024
43 checks passed
@mydea mydea deleted the fn/react-router-v6 branch February 5, 2024 16:39
mydea added a commit that referenced this pull request Feb 6, 2024
There is a proper replacement for all of them now.

Depends on:

* #10491
* #10489
* #10488
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants