-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add dev tooling #22
Add dev tooling #22
Conversation
Add a Perl script that creates the rustdocs for a version specific module it `types` e.g., `types/src/v17/mod.rs`.
a1e4ee1
to
5edaa24
Compare
Add a tool to help verify that what we have done is correct. Adds crate that when run produces: ```bash Verifying support for Bitcoin Core v17 Checking he documented methods are correct for this version of Core ... ✓ The documented status is correct ... ✓ ``` Run the tool for v17 module and fix the few mistakes it found - WIN! Then fix up the docs in v18 and run the tool to verify the v18 stuff is correct.
5edaa24
to
4fdea9c
Compare
Ugh, I clicked merge instead of ack'ing and using the merge script. |
Just crossed my mind that you have been gracious in helping me out with this crate @apoelstra, I merged this to save you the time/effort of looking at it. Didn't mean to brush you. I figured its easier to just pull master and play with the |
Yeah, no problem. I don't want to hold you up with process. But if I see stuff that's open I'll probably take a quick look and run through my local CI. |
This PR broke Cargo-minimal.lock (and maybe the other one) by adding the MSRV-incompatible |
Oh I should have excluded it from the workspace, woops. How did that pass CI I wonder. |
Fixed in #35 |
Add two new tools
types/src/v17/mod.rs
verify
tool that parses the RPC text file and then greps the codebase doing various checks.The
verify
tool is so that one can look at the docs for version specific types (the list of method names and implementation status) and have confidence that they are correct.I'm going to merge and release this without review because its just an additional unreleased dev tool. The fixes included in this PR are what I wanted to have confidence in the next release.
The next thing I want to verify is that the methods documented as returning nothing or stdlib types really do so by either hitting Core or grepping the source ... one day.