refactor(cli): simplify bip cli args#1554
Conversation
Coverage Report for CI Build 25796631085Coverage remained the same at 85.294%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
edec5fb to
0ba27ca
Compare
|
tACK can you squash your commits in other to follow the contribution guidelines |
a803aec to
a7d5ecb
Compare
I wanted to keep each change atomic. |
This is such a small change that it doesn't apply, atomicity here is more of "a pr should do only one thing and not multiple unrelated things " also even for bigger changes. from our merge history, you can see that it eventually get squashed into one commit before merge |
- `Option<bool>` -> `bool`. with `ArgAction::SetTrue` the flag
is `true` when present and `false` when absent. `None` was
a state the parser could never produce.
- drop `action = clap::ArgAction::SetTrue`. clap default to
`SetTrue` for a plain `bool` field.
- drop `long = "bipNN"`. clap derive it from the field name.
- drop `Clone` and `Deserialize`. both were dead code: `Flags`
is never cloned or deserialized.
Also changed:
- update payjoin-cli README
- remove rustdoc on `BitcoindWallet` mentioning a non-existent
`PayjoinWallet` trait
a7d5ecb to
7aa7e48
Compare
Got it. |
|
i think this is ready to get merged |
wait, where does it say this? it mentions hygienic commits following bitcoin core's reccomendations, which usually means to not squash when changes are not related |
For future reference the size of the change doesnt matter. if two changes are unrelated they should be in seperate commits |
Closes #1530
Simplify
--bip77/--bip78args, drop redundant clap attributes.The cli api didn't change, just internal refactoring.
I used Claude Code for research, but wrote all changes manually.
Pull Request Checklist
Please confirm the following before requesting review: