Skip to content

fix: warn and confirm when optional pickId fetch fails#229

Draft
bukinoshita wants to merge 2 commits intomainfrom
fix/pickid-optional-fetch-failure-1e69
Draft

fix: warn and confirm when optional pickId fetch fails#229
bukinoshita wants to merge 2 commits intomainfrom
fix/pickid-optional-fetch-failure-1e69

Conversation

@bukinoshita
Copy link
Copy Markdown
Member

@bukinoshita bukinoshita commented Apr 9, 2026

Summary by cubic

Warns and requires explicit confirmation when pickId (optional mode) fails to load items, preventing silent scope drops. Prevents unscoped API keys or topic-less broadcasts when fetches fail.

  • Bug Fixes
    • Show a warning with the fetch error and prompt to continue without scope (default is No).
    • Abort if the user cancels or declines; only continue without scope on explicit confirmation.
    • Include the resource name in the confirmation message for clarity.

Written for commit fbe1e52. Summary will update on new commits.

cursoragent and others added 2 commits April 9, 2026 17:31
Previously, when pickId was called in optional mode and the fetch failed,
it silently returned undefined. This caused callers like api-keys create
to proceed without domain scoping, creating broader-than-intended API keys.

Now, when a fetch fails in optional mode, the user sees a warning with the
error message and must explicitly confirm continuing without scope.
Declining or cancelling the confirmation aborts the operation.

Fixes BU-614

Co-authored-by: Bu Kinoshita <bukinoshita@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants