Reads now track the file opened separately from the file reported, across all file types.
What's wrong with this entry?
Reads now take a separate path to actually open, falling back to the resolved path when there isn't one, and fire a callback once the bytes are off disk. This applies to notebooks, images, PDFs and plain text alike.
- Bookkeeping for handover reads is skipped when the call came from another session.
- Image decoding picks a different reader on that remote path.
afterBytesRead
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.227
"Did you mean" file suggestions no longer block on a directory scan
Both mention file tool
-
v2.1.242
PDF reads return the document and page images
Both mention file tool
-
v2.1.248
Edit tool drops two validation branches
Both mention file tool