Expand description
oximemo-core: the pure-Rust heart of oximemo.
This crate owns the file store (source of truth), the derived metadata and
search indexes, file-watching, and synchronization. It knows nothing about
Tauri or clap; the desktop app and the CLI are thin adapters over the
vault::Vault facade.
Re-exports§
pub use assets::AssetInfo;pub use assets::AssetRef;pub use config::Theme;pub use config::VaultConfig;pub use error::CoreError;pub use error::Result;pub use memo::Cursor;pub use memo::Facets;pub use memo::IndexStats;pub use memo::Memo;pub use memo::MemoFilter;pub use memo::MemoHash;pub use memo::MemoId;pub use memo::MemoStats;pub use memo::MemoSummary;pub use memo::Page;pub use paths::Paths;pub use vault::DoctorReport;pub use vault::Vault;
Modules§
- assets
- Image asset storage for the vault.
- config
- Vault configuration parsed from
config.toml(§5.8). - error
- Error model for oximemo-core.
- hash
- Content hashing with deterministic normalization (§5.3).
- lock
- Process-local + cross-process advisory locking (§5.7).
- memo
- Domain model: notes, identifiers, categories, pagination.
- paths
- Filesystem layout for a vault and its derived index (§5.1, §5.2).
- store
- Storage layer: source-of-truth files plus derived indexes.
- sync
- Synchronization records and the dedup algorithm (§9.2).
- tags
- Inline
#tagextraction from note bodies (§3). - vault
- The
Vaultfacade: the single entry point both the CLI and the Tauri app use. It coordinates the file store (source of truth) with the derived redb + tantivy indexes, guarded by a cross-process advisory lock (§5.7). - watcher
- Vault file watcher (§5.5).