mirror of
https://github.com/getpaseo/paseo.git
synced 2026-10-24 18:22:38 +00:00
Mohamed Boudra
6e57bb1e4f
Two reproduced failures from the full correctness review. An empty result claimed the whole workspace had been read. Ripgrep never opens a file above the host's per-file ceiling, so a workspace whose only match lives in a large log answered "No matches" with nothing else said, and adding a small match still reported a complete result. The response now carries the ceiling the host actually applied, and the empty state names it. Only the empty state, because that is the only place the UI claims completeness; a populated list already claims nothing, and the occurrence-cap notice stays what it was. No permanent scope strip returns. A file literally named "a\b.txt" previewed itself and then opened "a/b.txt". The client rewrote every backslash to a separator on paths the host had already made canonical, so a valid Unix file name became a directory and a different file opened under a false "File changed" notice. Identity is now kept as the producer gave it: the daemon renders workspace-relative paths with its own separator turned into "/" for content search the way the file explorer already did, and the client only normalises separators for a path whose own shape is Windows, never from the client's operating system. Native source previews sized every row at a hard-coded 20px while the row is really one line at the reader's configurable code size, so scrolling to a match landed in the wrong part of the file. The height is derived from the size the view is already handed. Revealing a match thousands of lines into a long file remains broken on Android beyond this; that is recorded with device evidence rather than claimed fixed.
@getpaseo/protocol
Shared Paseo protocol schemas, codecs, and wire types.
Stability
This package is public so Paseo's published packages can depend on it cleanly. It is not a stable public API yet.
Schemas, exports, wire helpers, and types may change or disappear in any release without advance notice. Use it outside Paseo at your own risk until the package is explicitly documented as stable.