Index extensions and descriptions in plugin search

Build the search string from each plugin's description, config key, file
extensions/names, and — for exec-style plugins — the extensions and
commands under configItems. So "scss", "python", or "zig" now find the
right plugin, not just its name or URL.

Author: dsherret

homeView.tsx

@@ -95,6 +95,28 @@ function renderPage(pluginsData: PluginsData) {
   );
 }
 
+// builds the lowercased string the search filters against: name, url, version,
+// description, config key, and every file extension / file name / exec command
+// the plugin handles.
+function pluginSearchText(plugin: PluginData) {
+  const parts: (string | undefined)[] = [
+    plugin.name,
+    plugin.url,
+    plugin.version,
+    plugin.description,
+    plugin.configKey,
+    ...(plugin.fileExtensions ?? []),
+    ...(plugin.fileNames ?? []),
+  ];
+  for (const item of plugin.configItems ?? []) {
+    parts.push(...(item.match?.fileExtensions ?? []));
+    for (const command of item.config?.commands ?? []) {
+      parts.push(command.command, ...(command.exts ?? []));
+    }
+  }
+  return parts.filter(Boolean).join(" ").toLowerCase();
+}
+
 function renderCommands() {
   const commands: { cmd: string; desc: string }[] = [
     { cmd: "dprint config update", desc: "Automatically updates the plugins in a config file." },
@@ -132,7 +154,7 @@ function renderPlugins(data: PluginsData) {
 
 function renderPlugin(plugin: PluginData) {
   return (
-    <div class="plugin-row" role="row" key={plugin.name} data-search={`${plugin.name} ${plugin.url}`.toLowerCase()}>
+    <div class="plugin-row" role="row" key={plugin.name} data-search={pluginSearchText(plugin)}>
       <div class="col-name" role="cell">
         <span class="swatch"></span>
         <span class="name-text">{plugin.name}</span>

readInfoFile.ts

@@ -16,6 +16,19 @@ export interface PluginData {
     currentVersion: number;
     allVersions: number;
   };
+  // descriptive fields carried over from info.json, used to index the search
+  description?: string;
+  configKey?: string;
+  fileExtensions?: string[];
+  fileNames?: string[];
+  // present on plugins like exec where the real extensions/commands live in
+  // per-match config rather than top-level fileExtensions
+  configItems?: PluginConfigItem[];
+}
+
+interface PluginConfigItem {
+  match?: { fileExtensions?: string[] };
+  config?: { commands?: { command?: string; exts?: string[] }[] };
 }
 
 interface CacheEntry {