mirror of
https://github.com/narrrl/proton-drive-linux.git
synced 2026-11-11 01:17:03 +01:00
Nothing stopped `/`, the home folder, the Proton Drive mount, the app's own state or cache, or a folder nested in another root from becoming a sync root, and a restore took a path from another machine's profile as it was. One validator, `syncroot::problem`, now runs where roots are added and restored, on paths resolved through symlinks with `..` refused (B234).
37 lines
909 B
Rust
37 lines
909 B
Rust
//! Core building blocks for the Proton Drive Linux client: static client
|
|
//! identity, XDG paths, and the login/session/keyring layer that every
|
|
//! front-end (CLI today, daemon + GUI later) shares.
|
|
|
|
pub mod access;
|
|
pub mod auth;
|
|
pub mod batch;
|
|
pub mod cache;
|
|
pub mod config;
|
|
pub mod control;
|
|
pub mod db;
|
|
pub mod error;
|
|
pub mod kernelkey;
|
|
pub mod localindex;
|
|
pub mod menu;
|
|
pub mod mounts;
|
|
pub mod opener;
|
|
pub mod places;
|
|
pub mod profile;
|
|
pub mod sdkcache;
|
|
pub mod search;
|
|
pub mod service;
|
|
pub mod shell;
|
|
pub mod similar;
|
|
pub mod syncignore;
|
|
pub mod syncroot;
|
|
pub mod takeout;
|
|
pub mod tray;
|
|
|
|
pub use access::{Access, access_for, perm_bits};
|
|
pub use error::{CoreError, CoreResult, Error, Result};
|
|
|
|
// Re-export the SDK surface downstream crates need, so they depend on
|
|
// `pdfs-core` rather than pinning the SDK directly.
|
|
pub use proton_drive_rs::{self, Node, NodeKind, ProtonDriveClient};
|
|
pub use proton_sdk;
|