Conversation
Agents currently loop `issue view` per ID. Match `event view` with space-separated/newline IDs and a JSON array only for multi-id calls, without changing the shared single-id positional used by explain/plan/resolve. Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Member
I'd say it should open all up to a limit and the limit can be bypassed with |
Member
I'd also make this support multiple issues |
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.
Summary
sentry issue viewnow accepts multiple IDs in one invocation, the same wayevent viewalready does: space-separated args, newline-separated tokens inside a single arg, bounded parallel fetches, and JSON that stays a flat object for one ID and becomes an array when more than one was requested.The shared
issueIdPositionaltuple is unchanged, soexplain/plan/resolve/unresolve/archive/eventsstay single-id. Commas are not split (they can be part of a value).--webstill opens only the first issue.Test plan
sentry issue view FRONT-ABC --jsonstill returns a single object (shortIdat the top level)sentry issue view FRONT-ABC BACK-2 --jsonreturns a 2-element arraysentry issue view $'FRONT-ABC\nBACK-2' --jsonmatches two separate argssentry issue view FRONT-ABC,BACK-2is treated as one identifier, not twosentry issue view A B -wopens only A and warns that extras are ignoredsentry issue explain A Bis still single-id (shared positional untouched)Made with Cursor