-
Notifications
You must be signed in to change notification settings - Fork 12
refactor: clean dash core and hashes for warnings and clippy #109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
f03f52a
cd85a28
bb5a2c3
c4ad177
e223e26
8fe78aa
1a53abd
538e825
97be886
c32c354
4f15119
01514c9
599b9ed
76fdbd2
38b01e7
f56d9e1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,13 +2,13 @@ | |
| "strict_check_crates": [ | ||
| "key-wallet", | ||
| "key-wallet-manager", | ||
| "key-wallet-ffi" | ||
| "key-wallet-ffi", | ||
| "dash", | ||
| "hashes" | ||
| ], | ||
|
Comment on lines
+5
to
8
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🛠️ Refactor suggestion Moving dash and hashes into strict checks is good, but CI doesn’t consume this file. Right now, rust.yml hard-codes crate lists and never reads this JSON. These additions won’t enforce anything unless the workflow parses this file. Wire rust.yml to read strict_check_crates from this JSON (see suggested changes in rust.yml comment). This avoids drift and ensures “dash” and “hashes” are actually denied on warnings. |
||
| "excluded_crates": [ | ||
| "dash", | ||
| "dash-network", | ||
| "dash-network-ffi", | ||
| "hashes", | ||
| "internals", | ||
| "fuzz", | ||
| "rpc-client", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Validate crate names match Cargo package names.
The workflow currently refers to “dashcore_hashes” and “dashcore”, but this file lists “dash” and “hashes”. If package names don’t match exactly, the CI gating will silently misbehave.
Run:
If the actual packages are “dashcore”/“dashcore-hashes” (or similar), update either this JSON or the workflow accordingly.
🏁 Script executed:
Length of output: 330
🏁 Script executed:
Length of output: 3127
Update strict_check_crates to match actual Cargo package names
The entries in .github/strict-checks.json for “dash” and “hashes” don’t correspond to any Cargo packages in the workspace. According to your Cargo.toml manifests, the actual crate names are “dashcore” and “dashcore_hashes”.
Please update the JSON accordingly:
Locations to verify:
After this change, re-run the CI to ensure the strict-check workflow picks up both crates correctly.
📝 Committable suggestion
🤖 Prompt for AI Agents