ref(trends): remove v1 trends endpoint callers and dead code#112770
Draft
ref(trends): remove v1 trends endpoint callers and dead code#112770
Conversation
github-actions
bot
added
the
Scope: Frontend
cvxluo
force-pushed
the
cvxluo/remove-v1-trends-endpoint-callers-and-dead-code
branch
from
4741290 to
e3d571e
Compare
The v1 events-trends-stats endpoint is no longer called by any frontend code path. Always route to events-trends-statsv2 in TrendsDiscoverQuery, remove the withBreakpoint prop from trendChart components, and simplify the dead trendsWidget to always use v2 filters. Co-authored-by: Claude <noreply@anthropic.com>
cvxluo
force-pushed
the
cvxluo/remove-v1-trends-endpoint-callers-and-dead-code
branch
from
e3d571e to
e4791b1
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Complete the v1 trends endpoint deprecation started by PR #111146:
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.