10000 Standarise how individual tattoys handle and return errors · Issue #80 · tombh/tattoy · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Standarise how individual tattoys handle and return errors #80

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.

Sign up for GitHub

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

Jump to bottom
Open
tombh opened this issue May 25, 2025 · 0 comments
Open

Standarise how individual tattoys handle and return errors #80

tombh opened this issue May 25, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@tombh
Copy link
Owner
tombh commented May 25, 2025
  • Each tattoy should be responsible for handling all its errors, logging them and send UI notifications.
  • Tattoys should always strive to return Ok(()), not doing so should be considered an unhandled error.
  • Each tattoy should handle its own panics.

Is there a way to unify this? Like if a tattoy implemented a trait that did all this for us? I think the reason is that I got bogged down by async traits and getting them to work with tokio::task::Joinset.join_next().

See https://github.com/tombh/tattoy/blob/main/crates/tattoy/src/loader.rs
@tombh tombh added the enhancement New feature or request label May 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tombh
0