feat(findings): add resolution emojis, refine details panel, bump to 1.3.2

Add ✅/❌ emoji indicators for true/false positive resolutions in the
resolved findings tree. Shrink default description rows to 2, clean up
recommendation template whitespace, wire dropdown input events for
non-persistent field changes, and force-install in install.sh.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: bsamuels453

README.md

@@ -90,7 +90,7 @@ You can quickly navigate through all partially audited regions in your workspace
 
 You can fill detailed information about a finding by clicking on it in the _List of Findings_ view in the sidebar. The respective _Finding Details_ panel will open, where you can fill the information.
 The panel also shows a read-only provenance field (defaulting to "human"), with the author's username shown next to it.
-The Description, Exploit Scenario, and Recommendations fields auto-expand as you type, up to half the panel height, then scroll.
+The Description, Exploit Scenario, and Recommendations fields auto-expand as you type, starting at roughly two lines tall, up to half the panel height, then scroll.
 The action buttons at the top let you triage findings (True/False Positive), resolve notes, or open a GitHub issue.
 Resolution changes are applied through those action buttons.
 
@@ -111,7 +111,7 @@ In the _List of Findings_ view, multi-location entries are collapsed by default;
 
 ### Resolve and Restore
 
-Notes can be resolved from the _List of Findings_ panel. Findings are triaged instead: mark them as `True Positive` or `False Positive` from the same panel. Resolved notes and triaged findings are no longer highlighted in the editor but remain visible in the _Resolved Findings_ panel with a status badge. You can restore any resolved entry by clicking the corresponding `Restore` button in the _Resolved Findings_ panel.
+Notes can be resolved from the _List of Findings_ panel. Findings are triaged instead: mark them as `True Positive` or `False Positive` from the same panel. Resolved notes and triaged findings are no longer highlighted in the editor but remain visible in the _Resolved Findings_ panel with a status badge and a ✅/❌ indicator for true/false positives. You can restore any resolved entry by clicking the corresponding `Restore` button in the _Resolved Findings_ panel.
 
 ![Resolve and Restore](media/readme/gifs/resolve_finding.gif)
 

install.sh

@@ -1,3 +1,3 @@
 npx vsce package
 mv weaudit-*.vsix weaudit.vsix
-code --install-extension weaudit.vsix
+code --install-extension weaudit.vsix --force

package.json

@@ -2,7 +2,7 @@
     "name": "weaudit",
     "displayName": "weAudit",
     "description": "Bookmark findings and quickly navigate to areas of interest in the codebase",
-    "version": "1.3.1",
+    "version": "1.3.2",
     "publisher": "trailofbits",
     "author": "Trail of Bits",
     "categories": [],

src/panels/findingDetails.html

@@ -60,7 +60,7 @@
             </vscode-dropdown>
         </div>
     </div>
-    <div class="detailsDiv"><vscode-text-area placeholder="The finding details" id="description-area" rows="5">Description</vscode-text-area></div>
+    <div class="detailsDiv"><vscode-text-area placeholder="The finding details" id="description-area" rows="2">Description</vscode-text-area></div>
     <div class="detailsDiv"><vscode-text-area placeholder="The exploit scenario" id="exploit-area" rows="2">Exploit Scenario</vscode-text-area></div>
-    <div class="detailsDiv"><vscode-text-area value="Short term, \nLong term,\n" id="recommendation-area" rows="2">Recommendations</vscode-text-area></div>
+    <div class="detailsDiv"><vscode-text-area value="Short term,\nLong term," id="recommendation-area" rows="2">Recommendations</vscode-text-area></div>
 </div>

src/resolvedFindings.ts

@@ -27,6 +27,28 @@ function getResolutionBadge(entry: FullEntry): string {
     return "UNCLASSIFIED";
 }
 
+/**
+ * Returns an emoji that reflects the resolution status for resolved findings.
+ * @param entry The resolved entry to label.
+ * @returns An emoji for the resolution, or an empty string when not applicable.
+ */
+function getResolutionEmoji(entry: FullEntry): string {
+    if (entry.entryType !== EntryType.Finding) {
+        return "";
+    }
+
+    if (entry.details?.resolution === EntryResolution.TruePositive) {
+        return "✅";
+    }
+
+    const resolutionValue = String(entry.details?.resolution);
+    if (entry.details?.resolution === EntryResolution.FalsePositive || resolutionValue === "False Positive" || resolutionValue === "False Negative") {
+        return "❌";
+    }
+
+    return "";
+}
+
 export class ResolvedEntriesTree implements vscode.TreeDataProvider<FullEntry> {
     private resolvedEntries: FullEntry[];
 
@@ -59,7 +81,8 @@ export class ResolvedEntriesTree implements vscode.TreeDataProvider<FullEntry> {
     }
 
     getTreeItem(entry: FullEntry): vscode.TreeItem {
-        const label = entry.label;
+        const resolutionEmoji = getResolutionEmoji(entry);
+        const label = resolutionEmoji ? `${resolutionEmoji} ${entry.label}` : entry.label;
         const treeItem = new vscode.TreeItem(label, vscode.TreeItemCollapsibleState.None);
         if (entry.entryType === EntryType.Note) {
             treeItem.iconPath = new vscode.ThemeIcon("bookmark");

src/test/types.test.ts

@@ -55,7 +55,7 @@ describe("types.ts", () => {
             assert.strictEqual(details.type, FindingType.Undefined);
             assert.strictEqual(details.description, "");
             assert.strictEqual(details.exploit, "");
-            assert.strictEqual(details.recommendation, "Short term, \nLong term, \n");
+            assert.strictEqual(details.recommendation, "Short term,\nLong term,");
             assert.strictEqual(details.resolution, EntryResolution.Open);
             assert.ok(details.provenance);
             if (typeof details.provenance !== "object" || details.provenance === null) {

src/types.ts

@@ -256,7 +256,7 @@ export function createDefaultEntryDetails(commitHash?: string): EntryDetails {
         type: FindingType.Undefined,
         description: "",
         exploit: "",
-        recommendation: "Short term, \nLong term, \n",
+        recommendation: "Short term,\nLong term,",
         resolution: EntryResolution.Open,
         provenance: {
             source: "human",

src/webview/findingDetailsMain.ts

@@ -38,12 +38,15 @@ function main(): void {
 
     const severityDropdown = document.getElementById("severity-dropdown") as Dropdown;
     severityDropdown?.addEventListener("change", handlePersistentFieldChange);
+    severityDropdown?.addEventListener("input", handleNonPersistentFieldChange);
 
     const difficultyDropdown = document.getElementById("difficulty-dropdown") as Dropdown;
     difficultyDropdown?.addEventListener("change", handlePersistentFieldChange);
+    difficultyDropdown?.addEventListener("input", handleNonPersistentFieldChange);
 
     const typeDropdown = document.getElementById("type-dropdown") as Dropdown;
     typeDropdown?.addEventListener("change", handlePersistentFieldChange);
+    typeDropdown?.addEventListener("input", handleNonPersistentFieldChange);
 
     // for the text areas, we listen to to both the change and input events
     // on change events we persist the data into disk