You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
- Resolves CLI-T4: share issue URLs like
`https://{org}.sentry.io/share/issue/{shareId}/` now work with `sentry
issue view`, `explain`, and `plan`
- Two-step resolution: public share API → numeric group ID →
authenticated full-issue fetch
- Supports SaaS subdomain, bare `sentry.io`, self-hosted, and region
subdomain share URLs
## How it works
1. **URL parsing** (`sentry-url-parser.ts`): New `matchSharePath()` +
share branch in `matchSubdomainOrg()` recognize
`/share/issue/{shareId}/` paths
2. **Arg parsing** (`arg-parsing.ts`): New `"share"` variant in
`ParsedIssueArg` carries `shareId`, optional `org`, and `baseUrl`
3. **API** (`api/issues.ts`): `getSharedIssue()` calls the public `GET
/api/0/shared/issues/{shareId}/` endpoint (no auth needed) to get the
`groupID`
4. **Resolution** (`issue/utils.ts`): `resolveShareIssue()` fetches
groupID via share API, then uses the authenticated API for full issue
details with proper region routing
## Type change
`ParsedSentryUrl.org` is now optional since share URLs on bare domains
lack org context. Guards added in `issueArgFromUrl()`,
`orgProjectFromUrl()`, and `event/view.ts`.
0 commit comments