Plan sentry cli api endpoint usage#2782
Closed
szokeasaurusrex wants to merge 2 commits intomasterfrom
Closed
Conversation
Co-authored-by: daniel.szoke <daniel.szoke@sentry.io>
|
Cursor Agent can help with this pull request. Just |
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
2 participants
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.
Add
plan.mddetailing a comprehensive strategy to identify all Sentry CLI API endpoints.The plan ensures all API calls are identified by focusing on the
src/api/module as the single source of truth for HTTP requests. It outlines a step-by-step process usingripgrepfor static analysis, cross-referencing with integration tests, and proposing CI guardrails to prevent future omissions, addressing dynamic and region-specific URLs.