feat(package-vulnerability-scanner): surface account load errors and setup state - #455
Draft
amylin1249 wants to merge 2 commits into
Draft
feat(package-vulnerability-scanner): surface account load errors and setup state#455amylin1249 wants to merge 2 commits into
amylin1249 wants to merge 2 commits into
Conversation
This was referenced Jul 29, 2026
amylin1249
force-pushed
the
pvs-03-user-store-and-errordetail
branch
from
July 29, 2026 17:50
a5fb817 to
60ef612
Compare
Contributor
Extension release summary😴 Changed but won't releaseThe following extensions have code changes but the manifest version hasn't been incremented:
If you intended to release these changes, update the See the contributing guide for details. |
amylin1249
marked this pull request as draft
July 31, 2026 15:43
amylin1249
force-pushed
the
pvs-03-user-store-and-errordetail
branch
from
August 1, 2026 01:24
60ef612 to
ae2d6f5
Compare
amylin1249
force-pushed
the
pvs-03-user-store-and-errordetail
branch
4 times, most recently
from
August 1, 2026 05:46
c09d20d to
847cb98
Compare
…setup state Add errorDetail, a shared helper that prefers the backend's error detail over a generic status message, and use it in the user store. The store now tracks a distinct error state and a setupRequired flag (set on a 424, matching the missing-Visitor-API-Key case from the previous PR), instead of the previous bare fetch with no error handling at all. Wires tsconfig.vitest.json into tsconfig.json's references and npm test into CI now that a real test file exists.
amylin1249
force-pushed
the
pvs-03-user-store-and-errordetail
branch
from
August 1, 2026 15:45
847cb98 to
0e07598
Compare
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
1 participant
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.
Split out of #428 into small, reviewable PRs (tracking issue #415). Stacked 3/10 — stacked on #454, merge bottom-up.
Adds
errorDetail, a shared helper that prefers the backend's error detail over a generic status message, and uses it in the user store. The store now tracks a distinct error state and asetupRequiredflag (set on a 424), replacing a bare fetch with no error handling at all.