style: rustfmt the LC-78/LC-152 bridge files (LC-187) #250
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/lc-187-fmt-bridge-files"
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?
LC-187 standing CI fmt issue. CI Check workflow flagged formatting drift across the LC-78 / LC-152 bridge surfaces plus adjacent tests.
Source: the LC-78-AVATAR-PROXY (#245) and LC-152 SSRF (#246) merges landed without
cargo fmt --allover the whole workspace, so one-line shapes that the workspace-wide rustfmt wants wrapped slipped in.This PR is a pure
cargo fmt --allrun, no semantic changes.cargo check -p lets-chat-serverclean afterwards.21 files (8 src + 13 tests) under server/src/{bridge_avatar.rs, db/bridge_avatar_proxies.rs, db/bridges.rs, http_client.rs, routes/admin.rs, routes/api.rs, routes/bridge_avatar_media.rs, routes/room.rs} and server/tests/{bridge_avatar_fetch.rs, db_bridge_avatar_proxies.rs, lc152_.rs, outgoing_webhook_actor_payload.rs, routes_admin_bridges.rs, routes_api_bridge_.rs, routes_api_pagination.rs, routes_bridge_role_isolation.rs, routes_media_bridge_avatar_proxy*.rs, spike_image_decoder_hostile_corpus.rs}.
Note: there is a separate pre-existing clippy
too_many_argumentsviolation onresolve_msg_authorinserver/src/routes/mod.rs:154that the CI Check workflow also flags. Out of scope for this PR (different fix shape - either#[allow]or a struct-of-args refactor); will follow up in a separate commit under LC-187.🤖 Generated with Claude Code