Fix code lens issue when plugin name is invalid. Closes #118 (#121)

Closes #118

Author: garrytrinder

CHANGELOG.md

@@ -29,6 +29,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Setting: `devproxytoolkit.versionPreference` renamed to `dev-proxy-toolkit.version`
 
+### Fixed:
+
+- Code Lens: Fixed issue with documentation link shown for plugins with invalid names
+
 ## [0.8.0] - 2024-09-06
 
 ### Changed:

src/codelens.ts

@@ -1,6 +1,7 @@
 import * as vscode from 'vscode';
 import { isConfigFile, getASTNode, getRangeFromASTNode } from './helpers';
 import parse from 'json-to-ast';
+import { pluginSnippets } from './constants';
 
 export const registerCodeLens = (context: vscode.ExtensionContext) => {
   context.subscriptions.push(
@@ -49,13 +50,17 @@ export const createCodeLensForPluginNodes = (document: vscode.TextDocument) => {
         const pluginName = (pluginNameNode?.value as parse.LiteralNode)
           .value as string;
 
-        codeLens.push(
-          new vscode.CodeLens(getRangeFromASTNode(pluginNameNode), {
-            title: `📄 ${pluginName}`,
-            command: 'dev-proxy-toolkit.openPluginDoc',
-            arguments: [pluginName],
-          })
-        );
+        const isValidName = pluginSnippets[pluginName];
+
+        if (isValidName) {
+          codeLens.push(
+            new vscode.CodeLens(getRangeFromASTNode(pluginNameNode), {
+              title: `📄 ${pluginName}`,
+              command: 'dev-proxy-toolkit.openPluginDoc',
+              arguments: [pluginName],
+            })
+          );
+        }
       });
     }
   }