fix: improve formatting for SOL_BIP44_PREFIX handling in generate_crypto_multi_accounts
What changed, and why it matters
This commit is purely a code-formatting cleanup. It rewrites a single match arm in a Rust function so the condition and function call are split across multiple lines, matching the style of the surrounding code. No logic, constants, or behavior changed.
No security action needed. Treat as a normal style/refactoring commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In rust/apps/wallets/src/keystone_connect.rs, the match arm that checks whether a BIP44 path starts with SOL_BIP44_PREFIX was reformatted. The guard expression and the call to crate::backpack::generate_ed25519_key were broken into multi-line form. The exact same methods, variables, and arguments are used; only whitespace and line breaks differ.
Changed components
rust/apps/wallets/src/keystone_connect.rsInspect captured patch +11 / −2
diff --git a/rust/apps/wallets/src/keystone_connect.rs b/rust/apps/wallets/src/keystone_connect.rs
index 2484535..ed986bf 100644
--- a/rust/apps/wallets/src/keystone_connect.rs
+++ b/rust/apps/wallets/src/keystone_connect.rs
@@ -108,8 +108,17 @@ pub fn generate_crypto_multi_accounts(
Some("account.ledger_live".to_string()),
)?);
}
- _path if _path.to_string().to_lowercase().starts_with(SOL_BIP44_PREFIX) => {
- keys.push(crate::backpack::generate_ed25519_key(master_fingerprint, ele.clone(), None)?);
+ _path
+ if _path
+ .to_string()
+ .to_lowercase()
+ .starts_with(SOL_BIP44_PREFIX) =>
+ {
+ keys.push(crate::backpack::generate_ed25519_key(
+ master_fingerprint,
+ ele.clone(),
+ None,
+ )?);
}
_path
if _path
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.