-
Notifications
You must be signed in to change notification settings - Fork 38.7k
rpc, wallet: use the same next_index key in listdescriptors and importdescriptors
#26194
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
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. ConflictsNo conflicts as of last run. |
|
As it's an API change, probably should add it to the release-notes. |
src/wallet/rpc/backup.cpp
Outdated
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.
There should be some compatibility at least for a release or two.
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.
Done in b082f28.
80517c6 to
b9ea106
Compare
|
b9ea106 adds the |
aureleoules
left a comment
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.
ACK b9ea106f1da4e018ec4876d8e5b1209401ace382
src/wallet/rpc/backup.cpp
Outdated
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.
If this is kept for compatibility, it might be good to mention it, and that the value is equal to the other. Otherwise users might be confused to see the same field twice and wonder what the difference is?
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.
Done in b082f28.
b9ea106 to
b082f28
Compare
aureleoules
left a comment
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.
reACK b082f28
|
ACK b082f28 |
…istdescriptors` and `importdescriptors` b082f28 rpc, wallet: use the same `next_index` in listdescriptors and importdescriptors (w0xlt) Pull request description: Currently `listdescriptors` RPC uses `next` key to represent `WalletDescriptor::next_index` while `importdescriptors` uses `next_index`. This creates two different descriptor formats. This PR changes `listdescriptors` to use the same key as `importdescriptors`. ACKs for top commit: achow101: ACK b082f28 aureleoules: reACK b082f28 Tree-SHA512: c29ec59051878e614d749ed6dc85e5c14ad00db0e8fcbce3f5066d1aae85ef07ca70f02920299e48d191b7387024fe224b0054c4191a5951cb805106f7b8e37b
Currently
listdescriptorsRPC usesnextkey to representWalletDescriptor::next_indexwhileimportdescriptorsusesnext_index. This creates two different descriptor formats.This PR changes
listdescriptorsto use the same key asimportdescriptors.