-
Notifications
You must be signed in to change notification settings - Fork 266
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
json: add Other variant to SoftforkType #268
Conversation
Fixes rust-bitcoin#267. Without this variant, a call to `client.get_blockchain_info()` likely fails on some versions of bitcoind where other types of softfork deployments were active.
Lol, LGTM. If this were a field we expected to be used in the future I'd complain and say that the new variant should contain more information so that we can round-trip it. But I'll accept this for the sake of avoiding a parse error in old versions of Core (or litecoin). |
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 3f04a34
Will let @tcharding also chime in before merging. |
I did it this way with the same reasoning 😄 Adding more info in this variant would have added quite a lot of boilerplate code and effort. |
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 3f04a34
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 3f04a34
Fixes #267. Without this variant, a call to
client.get_blockchain_info()
likely fails on some versions ofbitcoind where other types of softfork deployments were active.