-
Notifications
You must be signed in to change notification settings - Fork 28
Add more examples #302
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 more examples #302
Conversation
CyberHoward
left a comment
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 is great! For the AsyncDaemon we can leave it as it is.
If we really need a good async implementation in the future we can create an AsyncTxHandler trait that's equivalent to the current TxHandler but is all async. But that's not worth doing at the moment.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
|
This PR aims at adding more examples and doc examples for users to interact with.
Issue with async daemon
It's difficult to interact with the async daemon and contracts
--> For instance, the upload needs an Uploadable argument, but it's not possible to create one with the AsyncDaemon because it doesn't implement TxHandler.
Should we remove that example or change AsyncDaemon a little ?
I don't think it's worth the effort to be honest