style: apply cargo fmt across src and tests #170
Loading…
Reference in a new issue
No description provided.
Delete branch "david/fix/pms-226-cargo-fmt"
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 check.yml CI job failed on cargo fmt --check (run #813), printing formatting diffs across src/ and tests/ files: import reordering (uuid::Uuid vs crate::modules::auth::TenantId) and call-site line-wrapping introduced by the PMS-139 TenantId sweep. Run cargo fmt --all to bring the tree back to canonical rustfmt output. No functional changes.
#PMS-226
Closing as redundant and stale. This PR's only commit was a
cargo fmtfixup (PMS-226). Two things have since happened inmain:The formatting intent is already served: PR #173 (
chore: cargo fmt --all after the PMS-139 TenantId sweep,c441b1c) and PR #183 (chore(fmt): apply cargo fmt --all after PMS-244..PMS-249 sweep) reformatted the whole workspace.The specific lines this PR reflows are obsolete. It wraps
TenantId::from_trusted(tenant_id)at the tickets notify/dispatch call sites, a transitional form. The tickets hub was fully migrated toTenantIdin PR #171 (sweep batch 8), somainnow passes the already-typedtenant_iddirectly. That divergence is the source of the merge conflict (insrc/modules/tickets/automation.rsandsrc/modules/tickets/service.rs); resolving towardmainloses nothing this PR intended, since it intended only formatting.It is an AGit PR with no server branch (head exists only at
refs/pull/170/head), so "Update Branch" was never available. Nothing left to merge.Pull request closed