fs/watch docs say response path is canonicalized but implementation returns request path
What happened?
The app-server README and protocol comment say fs/watch returns the canonicalized watched path.
However, the implementation returns params.path directly in FsWatchResponse, and existing tests assert the response path equals the requested path, including cases where the watch target may not yet exist.
This makes the docs/protocol comment misleading for clients that expect the response path to be canonicalized.
Expected behavior
Either fs/watch should canonicalize the response path before returning it, or the README/protocol comment should describe the current behavior and avoid promising canonicalization.
Additional context
I searched open issues and PRs for terms including fs/watch, canonicalized path, and FsWatchResponse, and did not find an existing open item that appears to cover this docs/implementation mismatch. A targeted local test run reported the relevant fs_watch tests passing.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗