Status
buckaroo_pick_file (crates/buckaroo-tauri/src/commands.rs:132-145) currently returns an error stub. The README acknowledges this:
buckaroo_pick_file() → `string | null` — stub; use tauri-plugin-dialog until v1.1
Filing for visibility / tracking — no urgency from my side (host apps can wire tauri-plugin-dialog themselves, which is what xorq-desktop will do).
Suggested resolution options
- Remove the stub and document
tauri-plugin-dialog as the official pattern; one fewer permission surface in the plugin.
- Implement it by re-exporting a thin wrapper around
tauri-plugin-dialog::FileDialogBuilder, scoped to common dataframe extensions (.parquet, .csv, .arrow, .feather, .ipc).
Option 1 is probably the right call — the dialog plugin is the standard, and bundling it inside buckaroo-tauri couples the crate to a UI concern. If kept as a stub, the README note should escalate from "until v1.1" to either a concrete milestone or a #[deprecated] attribute.
Status
buckaroo_pick_file(crates/buckaroo-tauri/src/commands.rs:132-145) currently returns an error stub. The README acknowledges this:Filing for visibility / tracking — no urgency from my side (host apps can wire
tauri-plugin-dialogthemselves, which is what xorq-desktop will do).Suggested resolution options
tauri-plugin-dialogas the official pattern; one fewer permission surface in the plugin.tauri-plugin-dialog::FileDialogBuilder, scoped to common dataframe extensions (.parquet,.csv,.arrow,.feather,.ipc).Option 1 is probably the right call — the dialog plugin is the standard, and bundling it inside
buckaroo-tauricouples the crate to a UI concern. If kept as a stub, the README note should escalate from "until v1.1" to either a concrete milestone or a#[deprecated]attribute.