Skip to content

feat(trace-view): Removing trace-view-v1 flag #94474

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

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

Abdkhan14
Copy link
Contributor

This PR removes all usage of the 'trace-view-v1' flag from the FE. It has been in full GA over the last couple quarters and we want the linked functionality to be enabled by default in self hosted.

@Abdkhan14 Abdkhan14 requested review from a team as code owners June 26, 2025 19:41
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jun 26, 2025
Copy link

codecov bot commented Jun 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #94474      +/-   ##
==========================================
+ Coverage   87.90%   87.99%   +0.08%     
==========================================
  Files       10441    10400      -41     
  Lines      603609   602710     -899     
  Branches    23491    23312     -179     
==========================================
- Hits       530574   530325     -249     
+ Misses      72669    71915     -754     
- Partials      366      470     +104     

const organization = OrganizationFixture({
features: ['trace-view-v1'], // only testing against new trace view
});
const organization = OrganizationFixture({});
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
const organization = OrganizationFixture({});
const organization = OrganizationFixture();

Copy link
Contributor

@edwardgou-sentry edwardgou-sentry left a comment

Choose a reason for hiding this comment

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

Lots of files but individual changes look ok to me. In the future, would be great if this could be split up a bit more (for example const organization = OrganizationFixture({}); changes could be its own pr), or if we had made prepared branching test changes incrementally as the trace view was being developed.

@@ -209,7 +209,7 @@ describe('Breadcrumbs', () => {

expect(screen.getByText('/settings/')).toHaveAttribute(
'href',
'/organizations/org-slug/insights/backend/project-slug:abcdabcdabcdabcdabcdabcdabcdabcd/?referrer=breadcrumbs'
'/organizations/org-slug/traces/trace/undefined/?referrer=breadcrumbs&statsPeriod=14d'
Copy link
Contributor

Choose a reason for hiding this comment

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

Any way we can add a mock somewhere so that the trace id isn't undefined? Feels like that should be part of the test. Unless this flow isn't valid anymore, in which case maybe it makes sense to just delete this test

@edwardgou-sentry
Copy link
Contributor

Acceptance tests are failing, but we spoke about this on slack. Seems like these are for the old event details page which is deprecated and should be removed.

@Abdkhan14 Abdkhan14 requested a review from priscilawebdev July 2, 2025 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants