Skip to content

tools/pathUtils

Paths as models write them: Unicode spaces, a leading @, and file names whose apostrophes or AM/PM spaces differ from what macOS stores.

Since v0.0.0


Like resolveToolPath, but the first spelling variant that exists, for reading.

Signature

declare const resolveReadToolPath: (env: ExecEnv, path: string) => Effect.Effect<string, FileError>

Source

Since v0.0.0

The absolute path a tool argument names.

Signature

declare const resolveToolPath: (env: ExecEnv, path: string) => Effect.Effect<string, FileError>

Source

Since v0.0.0