Skip to content

Address all TODO in v22 #295

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

jamillambert
Copy link
Collaborator

@jamillambert jamillambert commented Jul 15, 2025

Go through all the TODO in the v22 types table. Add all the missing RPCs.

Redefine listdescriptors in v25 due to added return field.

enumeratesigners and walletdisplayaddress RPCs require an external signer and have been left untested because of this. Opened #294.

The heading comment for raw_transactions was missing from verify v26.

Add it.
Add the struct to types.
Add the client macro.
Update the table to version, no model is required. Currently untested.
Add the reexports.
Add the struct, client macro, test and reexports.

Redefine the struct in v25 for added return field.

Change to no_model since there is nothing to model.
Add the struct, model, client macro, and reexports.

Currently untested.
pub internal: Option<bool>,
/// Defined only for ranged descriptors.
pub range: Option<[u64; 2]>,
/// The next index to generate addresses from; defined only for ranged descriptors.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
/// The next index to generate addresses from; defined only for ranged descriptors.
/// Same as `next_index` field. Kept for compatibility reason.

Address(ref e) => Some(e),
}
}
}
Copy link
Member

@tcharding tcharding Jul 15, 2025

Choose a reason for hiding this comment

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

We don't need all this error stuff man, we can just return the address::ParseError directly since there is only one error. I have a vague feeling you added a single field enum recently in some other PR and I missed observing this, correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants