Feat/issue 613 616 623 738 vscode tests verify deployment#933
Merged
Conversation
- Add `sanctifier.minSeverity` config (error|warning|information, default warning) so users control which severity levels appear as editor diagnostics - Expose a typed `SanctifierExtensionApi` from `activate()` (version + getFindings) for stable consumption by downstream extensions - Add persistent output channel for `analyzeWorkspace` results instead of opening an untitled document; CLI output streams there with debug context - Add `sanctifier.toggleEnable` command (status-bar clickable) and `sanctifier.showOutput` command for quick access to the log - Status bar item shows live finding count; clicking it toggles the extension - Add `filterBySeverity` / `SEVERITY_ORDER` utilities to analyzer module - Add content-change cache to skip re-analysis when document text is unchanged - Handle `onDidChangeWorkspaceFolders` to invalidate workspace detection cache - Extend test suite with 7 new tests covering filterBySeverity and SEVERITY_ORDER - Document the VS Code extension public API in DOCUMENTATION_INDEX.md
|
@christianahtemitope2005 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
@christianahtemitope2005 is attempting to deploy a commit to the gbangbolaoluwagbemiga's projects Team on Vercel. A member of the Team first needs to authorize it. |
Gbangbolaoluwagbemiga
merged commit 02afa98
into
HyperSafeD:main
11 of 25 checks passed
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
2 participants
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
src/types.tsand per-folder workspace detection tosrc/workspace.ts; replaced global boolean cache with per-folderMap<string, boolean>for proper multi-root workspace supportsrc/test/analyzer.test.ts) using Node's built-innode:testrunner with.rsfixture files covering S001 auth-gap, S002 panic, S006 unwrap, S003 arithmetic overflow, deduplication, and severity filtering (19 tests, all passing)testandlintscripts inpackage.jsonso the existing CI workflow (vscode-extension-ci.yml) now runs tests and type-checks on ubuntu/windows/macos with Node 24sanctifier verify-deployment#738 – Addedsanctifier verify-deploymentCLI subcommand: hashes local WASM (viastellar contract buildor cargo fallback) and compares against on-chain WASM fetched withstellar/sorobanCLI; supports--expected-hashto skip local build and--format jsonfor machine-readable outputTest plan
cd vscode-extension && npm ci && npm run compile && npm test— 19 unit tests passnpm run lint— no TypeScript errorscargo check -p sanctifier-cli— compiles without errorscargo test -p sanctifier-cli— sha256 unit tests passCloses #616, Closes #623, Closes #613, Closes #738