[sentry-junior]

Part of #1564.

Every command that still parses a positional inside func is now named on a lint allow-list with its follow-up, so the rest can be migrated one by one and no new one can appear. Release commands, the small straggler, move to a bound positional. A new table-driven test checks that commands taking IDs read the same inputs the same way.

Lint

• no-ad-hoc-id-arguments now also rejects parseIssueTarget and parseDashboardTarget in commands. These parsers only tag a positional for completion and leave the parsing to func.
• require-target-resolution now also rejects parseOrgTarget, parseOrgProjectTarget, parseOrgProjectArg, and the resolve{OrgOnly,OrgOptional,ProjectBound}FromArg helpers in commands.
• Both rules use allow-lists (AD_HOC_ID_PARSING_ALLOWED, UNBOUND_TARGET_PARSING_ALLOWED), and each entry names its follow-up. The lists only shrink: an allow-listed file that stops using the names gets "Remove this file from the allow-list".
• event view is no longer exempt, since ref(cli): Parse event view arguments with the shared ID grammar #1733 merged.
• ReleaseTarget was added to BOUND_TARGET_TYPES.
• New rule tests are in scripts/cli-lint-rules.test.mjs.

Release positional

releaseParameter(USAGE_HINT, brief) in release/parse.ts returns a bound ReleaseTarget. func reads { version, org, detectedFrom } from await target.resolved. A blank version now fails the parse (exit 252) instead of failing inside func. Migrated commands: archive, create, delete, deploy, deploys, finalize, restore, set-commits, view.

Cross-command conventions test

test/lib/argument-conventions.test.ts runs the same inputs through each command's own positional with applyBoundPositionals, the way Stricli does. The inputs are:

• a bare ID
• <x>/<id>
• <org>/<project>/<id>
• <org>/<project> <id>
• reversed arguments (expects a warning)
• extra or multiple IDs
• a missing ID (expects ArgumentParseError)
• a pasted URL (its server must be applied only when .resolved runs)

Commands covered: trace view/logs, span view/list, log view/list, event view, replay view/download, the single-issue commands (issue and feedback), and all release commands. Where a command legitimately differs, its row says how:

• slashTarget: "project" for span view, log view and event view
• multiple for span view, log view and event view
• optional for span list and log list
• separateTarget: false for span view
• no URL for log view

Audit: positional parsing in func

Excludes event view (#1733, merged) and dashboard/* (#1730).

Already on bound parsers (verified)

• trace view, trace logs (ref(cli): Parse list command targets in their positional #1711, ref(cli): Parse trace logs and span list arguments before they run #1728)
• span view, span list (ref(cli): Parse list command targets in their positional #1711, ref(cli): Parse trace logs and span list arguments before they run #1728)
• log view, log list: fully migrated in ref(cli): Parse every kind of ID argument with one grammar #1714. The remaining parseOrgProjectInput call is inside the bound parseLogListInput, not in func.
• replay view, replay download: fully migrated in ref(cli): Parse every kind of ID argument with one grammar #1714 (parseIdArgument is called inside the bound parser).
• Single-issue commands (issuePositional, ref(cli): Parse issue arguments with their own grammar, before the command runs #1729) and event view (ref(cli): Parse event view arguments with the shared ID grammar #1733)
• release * (9 commands): migrated in this PR

Allow-listed, still parsing in func

• issue view, issue explain (issue/utils.ts), issue merge: these take several issues and need an array issue positional (Consolidate target parsing into positional parsers #1564)
• alert issues create/delete/edit/view: [<org>/[<project>/]]<rule>, resolving to every matching project (Consolidate target parsing into positional parsers #1564: alert rule target)
• alert metrics create/delete/edit/list/view: [<org>/]<rule>, org-scoped (Consolidate target parsing into positional parsers #1564: alert rule target)
• agent-conversation view, integration delete: [<org>/]<id> with a non-hex ID, the same shape as releaseParameter (Consolidate target parsing into positional parsers #1564: org-scoped ID)
• org view, trial list, trial start: a bare org positional (Consolidate target parsing into positional parsers #1564: org positional)
• init, project create: a target followed by other positionals (Consolidate target parsing into positional parsers #1564)
• dashboard create, dashboard list/restore/revisions/view, dashboard widget add/delete/edit: covered by ref(cli): Parse dashboard and issue arguments with the shared ID grammar #1730. These entries will fail the ratchet once ref(cli): Parse dashboard and issue arguments with the shared ID grammar #1730 lands, and whichever PR merges second removes them.

Not target parsing, and not covered by these rules

• monitor run: args[0] is a monitor slug followed by a passthrough command. This is arity handling, not target parsing.
• Paths, endpoints, versions, selectors and doc parts: api, auth login/switch, build/debug-files/snapshots upload, debug-files find (debug IDs), docs *, help, local *, schema, cli upgrade, org list, react-native xcode, wasm-split.

Checks

pnpm run tsc and pnpm run lint pass, and the lint-rule tests pass (70/70). The new conventions test and the release and issue tests pass. The only full-suite failures locally are sandbox noise: tests that need to run without root, e2e and init-eval tests that need a build or keys, and timing-sensitive tests.

via BYK.

--

View Junior Session in Sentry

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-local	Ready	Preview	Oct 29, 2026 8:35pm UTC