feat: add VS Code inline warnings extension#77
Open
cybercraftsolutionsllc wants to merge 1 commit into
Open
Conversation
|
@patchledgerops-agent is attempting to deploy a commit to the Rapi's projects Team on Vercel. A member of the Team first needs to authorize it. |
6 tasks
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
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
isnad-scanon opened/saved files and maps scanner output into VS Code diagnosticsisnad-scanandisnad-scanner, document extension setup/package flow, and refresh scanner lockfile audit fixesValidation
npm run buildinscanner/npm testinvscode-extension/(5 node:test unit tests)npm run package -- --out isnad-inline-warnings-0.1.0.vsixinvscode-extension/npm audit --omit=dev --jsoninscanner/(0 vulnerabilities after lockfile update)git diff --checkMarketplace note
The extension is package-ready and includes the manifest, compiled entrypoint, license, diagnostics integration, tests, and VSIX packaging path. Publishing to the VS Code Marketplace still requires maintainer access to the
isnadpublisher account or a release workflow with that token, so I documented that final publish step instead of pretending to have maintainer credentials.Refs #6