Erik Kotsiuba
d6db94a39d
Update Pi packages to 0.79.9 and align pi-ask with current TUI/RPC behavior. - guard custom ask/settings flows to TUI mode with a clear non-TUI fallback - reset config cache on extension reload so edited settings are picked up - clean up remote ask flow listeners on session shutdown - forward editor focus/invalidation and keep @ file autocomplete explicit - document the non-TUI contract and cover the compatibility fixes with tests
53 lines
1.3 KiB
TypeScript
53 lines
1.3 KiB
TypeScript
import { accessSync, constants as fsConstants } from "node:fs";
|
|
import { delimiter, join } from "node:path";
|
|
import { CombinedAutocompleteProvider } from "@earendil-works/pi-tui";
|
|
|
|
const FD_BINARY_NAMES =
|
|
process.platform === "win32"
|
|
? ["fd.exe", "fdfind.exe", "fd", "fdfind"]
|
|
: ["fd", "fdfind"];
|
|
|
|
/**
|
|
* pi resolves fd internally for its main editor, but that resolver is not part of
|
|
* the public extension API. Custom editors therefore need to supply the fd path
|
|
* themselves when reusing CombinedAutocompleteProvider for `@` file mentions.
|
|
*/
|
|
export function createAskAutocompleteProvider(cwd: string) {
|
|
return Object.assign(
|
|
new CombinedAutocompleteProvider(
|
|
[],
|
|
cwd,
|
|
findAutocompleteBinary(FD_BINARY_NAMES)
|
|
),
|
|
{ triggerCharacters: ["@"] }
|
|
);
|
|
}
|
|
|
|
function findAutocompleteBinary(binaryNames: readonly string[]): string | null {
|
|
const pathValue = process.env.PATH;
|
|
if (!pathValue) {
|
|
return null;
|
|
}
|
|
|
|
const directories = pathValue.split(delimiter).filter(Boolean);
|
|
for (const binaryName of binaryNames) {
|
|
const executablePath = directories
|
|
.map((directory) => join(directory, binaryName))
|
|
.find(isExecutableFile);
|
|
if (executablePath) {
|
|
return executablePath;
|
|
}
|
|
}
|
|
|
|
return null;
|
|
}
|
|
|
|
function isExecutableFile(path: string): boolean {
|
|
try {
|
|
accessSync(path, fsConstants.X_OK);
|
|
return true;
|
|
} catch {
|
|
return false;
|
|
}
|
|
}
|