Skip to content

Conversation

@w0xlt
Copy link
Contributor

@w0xlt w0xlt commented Sep 28, 2022

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.

@DrahtBot
Copy link
Contributor

DrahtBot commented Sep 28, 2022

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Reviews

See the guideline for information on the review process.

Type Reviewers
ACK aureleoules, achow101

If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

Conflicts

No conflicts as of last run.

@furszy
Copy link
Member

furszy commented Sep 28, 2022

As it's an API change, probably should add it to the release-notes.

Copy link
Member

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done in b082f28.

@w0xlt w0xlt force-pushed the next_index_listdescriptors branch from 80517c6 to b9ea106 Compare November 1, 2022 22:36
@w0xlt
Copy link
Contributor Author

w0xlt commented Nov 1, 2022

b9ea106 adds the next_index instead of replacing next as suggested in #26194 (comment) for compatibility reasons and adds the release notes as suggested in #26194 (comment).

Copy link
Contributor

@aureleoules aureleoules left a comment

Choose a reason for hiding this comment

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

ACK b9ea106f1da4e018ec4876d8e5b1209401ace382

Copy link
Member

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done in b082f28.

@w0xlt w0xlt force-pushed the next_index_listdescriptors branch from b9ea106 to b082f28 Compare December 6, 2022 14:38
Copy link
Contributor

@aureleoules aureleoules left a comment

Choose a reason for hiding this comment

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

reACK b082f28

@achow101
Copy link
Member

achow101 commented Mar 8, 2023

ACK b082f28

@DrahtBot DrahtBot removed the request for review from achow101 March 8, 2023 17:08
@achow101 achow101 merged commit 1ff135c into bitcoin:master Mar 8, 2023
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Mar 8, 2023
…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
@bitcoin bitcoin locked and limited conversation to collaborators Mar 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants