nvrl c73d5c9436 refactor(fuse): reach Drive through a DriveApi trait ...

`Core` held a concrete `ProtonDriveClient`, so no test could make Drive
answer late, answer stale or not answer. This is the first step of
phase 0 in docs/MILESTONE-3.0.0.md.

`DriveApi` (`crates/pdfs-fuse/src/drive.rs`) covers the calls the sync
core makes: listings, events, creates, uploads, downloads, renames,
moves, trashes and restores. `ProtonDriveClient` implements it by
forwarding. `Core::drive` holds it, and every call of those methods now
goes through it. Sharing, Photos, devices, invitations and public links
stay on `Core::client`.

The trait takes readers and writers as trait objects, and
`impl dyn DriveApi` puts the client's generic signatures back, so call
sites read the same. Block reads go through `RevisionRead` instead of
the SDK's `RevisionReader`, which only the SDK can construct.

No behaviour change.

2026-10-03 04:37:37 +02:00

..

pdfs-cli

fix(cli): stop quietly when stdout is closed

2026-10-02 21:16:34 +02:00

pdfs-core

fix(fuse,core): fix B114 to B120 from the account runs

2026-10-03 02:10:23 +02:00

pdfs-fuse

refactor(fuse): reach Drive through a DriveApi trait

2026-10-03 04:37:37 +02:00

pdfs-gui

chore: point homepage metadata at proton-drive.narl.io

2026-09-29 05:30:38 +02:00