Skip to content

refactor: remove various Clippy warnings - #793

Merged
shumkov merged 2 commits into
v0.24-devfrom
fix/clippy
Feb 23, 2023
Merged

refactor: remove various Clippy warnings#793
shumkov merged 2 commits into
v0.24-devfrom
fix/clippy

Conversation

@jawid-h

Copy link
Copy Markdown
Contributor

Issue being fixed or feature implemented

Trying to remove Clippy warnings for easier future warnings elimination

What was done?

  • fixed code according to Clippy
  • kept unused variables as this is thing of discussion

How Has This Been Tested?

Breaking Changes

None

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

@jawid-h
jawid-h marked this pull request as ready for review February 20, 2023 12:50
Comment threadpackages/rs-drive-abci/tests/strategy_tests/upgrade_fork_tests.rs Outdated
Comment threadpackages/rs-drive/src/drive/grove_operations.rs Outdated
@jawid-h
jawid-h requested a review from shumkovFebruary 20, 2023 14:58

@shumkovshumkov left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@shumkovshumkov changed the title chore: remove various Clippy warningsrefactor: remove various Clippy warningsFeb 23, 2023
@shumkov
shumkov merged commit c49f6f2 into v0.24-devFeb 23, 2023
@shumkov
shumkov deleted the fix/clippy branch February 23, 2023 16:00
QuantumExplorer added a commit that referenced this pull request Jun 1, 2026
Adopts the network-scoped wallet id from rust-dashcore #793 (merged to
dev as 3d0d5dcd) to structurally fix the carried-forward blocking
finding #2: child caches keyed by the network-INDEPENDENT walletId
(PersistentTxo / PersistentPendingInput / PersistentAssetLock /
PersistentPlatformAddress / PersistentShieldedSyncState) cross-fed
state between a single mnemonic's per-network wallets.
With #793 the wallet id is network-scoped BY DEFAULT at construction
(`Wallet::from_mnemonic` / `from_seed` fold a domain-tagged, wire-stable
network byte into the digest), so the same mnemonic now yields a
DISTINCT id per network. Every walletId-keyed structure becomes
network-correct by construction — no networkRaw columns needed on the
child models, and the leak is eliminated at the source.
- Cargo.toml / Cargo.lock: pin all 8 rust-dashcore crates to 3d0d5dcd
(the squash-merge of #793 on dev).
- rs-platform-wallet: no behavior change needed — construction already
stamps the scoped id. `register_wallet` carries an explanatory
comment. Added two unit tests proving same-mnemonic → 4 pairwise-
distinct ids across networks, and stable per-(seed,network).
- CreateWalletView: the multi-network create now persists the mnemonic
+ metadata + `isImported` per FRESHLY-CREATED network's scoped
walletId (each is independently recoverable), instead of once under a
single shared id; metadata records just that network. All-already-
exist is a benign dismiss.
- WalletDetailView.enableNetwork: stores the mnemonic under the
newly-enabled network's scoped walletId so that wallet's own keychain
lookups resolve.
- PlatformWalletManager.deleteWallet: comment updated for the scoped-id
model (the walletRowCountAcrossNetworks guard stays correct).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@jawid-h@shumkov@antouhou