Skip to content

resolveAndValidatePath Shows Inverted Error Messages #47

@akramcodez

Description

@akramcodez

Description

The resolveAndValidatePath function throws incorrect error messages based on the error type.
Currently:

  • ENOENT (path not found) incorrectly throws "Failed to access"
  • Other errors like EACCES (permission denied) incorrectly throw "Path does not exist"

This leads to misleading feedback for users and makes debugging harder.

Location

  • File: packages/core/src/tools/grep.ts
  • File: packages/core/src/tools/ripGrep.ts

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions