-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add params member to JSON-RPC request #97
Conversation
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.
Looks good! I love the test - but it seems like a test that could benefit from parameterization. I'm just bringing it up now since I've run into a couple similar situations on my local branches. From what I can tell, rstest is probably the best crate to use for various testing utils. Even if it's not necessary for this test, it seems like a crate we'll want to use in other places as the project grows.
ed88f71
to
aae16cb
Compare
Let me tell you a secret, I stole this test from one json-rpc crate 😄 Good to know about |
Fair enough, but I have a feeling like we'll need it sooner or later. Also, it's often worthwhile to add some code complexity if it means improved / more granular tests. Obviously there's a limit somewhere. I don't think it's a blocker for merging this, but you might think about leaving a comment that these tests should be expanded at some point |
aae16cb
to
e1423f1
Compare
Probably you are right, updated the test with parametrization. |
6d2ad4a
to
3ba4de1
Compare
3ba4de1
to
4783277
Compare
@ogenev Looks great! Thanks for updating those tests. lgtm! |
Adds support for parsing parameters for the JSON-RPC call.
Fixes #96