config: re-export rusqlite for no-sync consumers
ConfigStore::open takes a Connection the caller must build, so a consumer
that only reads and writes config had to depend on rusqlite directly and
version-match it. Re-export it instead; the Alloy console links only this
crate.
2 files changed,
+6 insertions,
-1 deletion
| 1 |
1 |
|
[package]
|
| 2 |
2 |
|
name = "synckit-config"
|
| 3 |
|
- |
version = "0.1.0"
|
|
3 |
+ |
version = "0.1.1"
|
| 4 |
4 |
|
edition = "2024"
|
| 5 |
5 |
|
license-file = "LICENSE"
|
| 6 |
6 |
|
description = "Local key/value app settings with sync postures. The store half of SyncKit's config sync, usable with no network."
|
| 40 |
40 |
|
|
| 41 |
41 |
|
pub use spec::{ConfigSpec, PolicyRow, Posture};
|
| 42 |
42 |
|
pub use store::{ConfigError, ConfigStore, Result};
|
|
43 |
+ |
|
|
44 |
+ |
/// Re-exported so a consumer can open the [`Connection`](rusqlite::Connection)
|
|
45 |
+ |
/// that [`ConfigStore::open`] takes without depending on rusqlite itself, nor
|
|
46 |
+ |
/// version-matching it. A no-sync app (the Alloy console) links only this crate.
|
|
47 |
+ |
pub use rusqlite;
|