chore: workspace clippy + missing-field fix-up for preflight
Two small workspace-clippy gaps that snuck through the per-crate
sweeps in this branch:
* `crates/cli/src/lib.rs` — the OpenAI-provider passthrough test was
building a `ResolvedRuntimeOptions` literal directly and missed the
`yolo: Option<bool>` field that landed earlier on this branch in
665801bb8 (`fix(cli): forward --yolo to TUI binary`). Set to `None`
to match the test's non-yolo intent.
* `crates/tui/src/mcp.rs` — the new `reload_if_config_changed` swap
test was using `iter().any(|n| *n == "new")`, which is rust-1.94
clippy's `manual_contains` lint. Switched to `names.contains(&"new")`.
`cargo clippy --workspace --all-targets --all-features --locked --
-D warnings` is now green.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -2516,6 +2516,7 @@ mod tests {
|
||||
telemetry: false,
|
||||
approval_policy: None,
|
||||
sandbox_mode: None,
|
||||
yolo: None,
|
||||
http_headers: std::collections::BTreeMap::new(),
|
||||
};
|
||||
|
||||
|
||||
@@ -2781,7 +2781,7 @@ mod tests {
|
||||
assert!(reloaded, "content-changed config must trigger reload");
|
||||
let names = pool.server_names();
|
||||
assert!(
|
||||
names.iter().any(|n| *n == "new"),
|
||||
names.contains(&"new"),
|
||||
"expected new server in pool after reload, got {names:?}"
|
||||
);
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user