fix(settings): drop extra arg from RMM delete_lookup calls #235
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/mapps-226-delete-lookup-extra-arg"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The RMM admin UI (connections, device mappings, alert rules) called
delete_lookupwith a third&'static strlabel argument, but the helper's signature isdelete_lookup(id: &str, base: &str). This broke compilation with E0061 (3 arguments supplied, 2 expected) and failed clippy, the wasm check, and tests in check.yml. The label was redundant: each call site already names the entity in its error message ("Could not delete connection", etc.). Remove the third argument from all three call sites to match the function signature and the other ten lookup-editor call sites.#MAPPS-226
The RMM admin UI (connections, device mappings, alert rules) called `delete_lookup` with a third `&'static str` label argument, but the helper's signature is `delete_lookup(id: &str, base: &str)`. This broke compilation with E0061 (3 arguments supplied, 2 expected) and failed clippy, the wasm check, and tests in check.yml. The label was redundant: each call site already names the entity in its error message ("Could not delete connection", etc.). Remove the third argument from all three call sites to match the function signature and the other ten lookup-editor call sites. #MAPPS-226Superseded: the RMM delete_lookup arity fix landed on main via #237. Closing this duplicate.
Pull request closed