-
Notifications
You must be signed in to change notification settings - Fork 1
feat: rust implementation #19
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
Conversation
| } | ||
|
|
||
| #[test] | ||
| fn post_method() { |
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.
This could use some form_data tests
| mod get; | ||
| mod post; | ||
|
|
||
| pub fn get_client() -> PolywrapClient { |
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.
I like that we can now use the Rust client and don't have to rely on the JS client for rust wrappers.
Though, I think for most cases we could just mock the subinvocations(if any) and have unit tests instead of e2e
|
|
||
| #[plugin_impl] | ||
| impl Module for HttpPlugin { | ||
| fn get( |
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.
In general for wrappers (like we talked about on the call), I'd love to see more unit tests where we mock the deps (e.g. the subinvocations or in this case the network call).
This not only helps us test the code more thoroughly and without the client dep, but also I find it helps while developing.
No description provided.