feat(webhook): Add Webhook Examples #34
Conversation
| use helius::Helius; | ||
|
|
||
| #[tokio::main] | ||
| async fn main() { |
There was a problem hiding this comment.
This should have a return type. You could import Result from use helius::error::Result and use the type alias for the return type so the line reads async fn main() -> Result<()> {. You'll also have to add in Ok(()) at the end of the block to satisfy the return type. If you get confused, I recommend looking at the other examples we currently have for the SDK
|
|
||
| let webhook_id = "your_webhook_id"; | ||
| let new_addresses = ["your_address1".to_string(), "your_address2".to_string()]; | ||
| let response = helius.append_addresses_to_webhook(webhook_id, &new_addresses).await; |
There was a problem hiding this comment.
Can you make the response type explicit here, please?
examples/create_webhook.rs
Outdated
| }; | ||
|
|
||
| #[tokio::main] | ||
| async fn main() { |
There was a problem hiding this comment.
Same comment re main that was made in examples/append_address_to_webhook.rs. All of the example files should follow this convention
examples/create_webhook.rs
Outdated
| encoding: Default::default(), | ||
| }; | ||
|
|
||
| let response = helius.create_webhook(request).await; |
There was a problem hiding this comment.
Can you also make this response type explicit, please?
There was a problem hiding this comment.
And can you please make all the remaining response vars in the subsequent examples explicit, please?
There was a problem hiding this comment.
It should be good now
This pull request adds examples of webhook functions to the project. The new examples demonstrate how to implement and use webhooks effectively, providing clear and practical usage scenarios.
These additions aim to help developers understand and implement webhook functionality more easily.