Skip to content
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

Signals #104

Closed
wants to merge 8 commits into from
Closed

Signals #104

wants to merge 8 commits into from

Conversation

RealOrangeOne
Copy link
Owner

Use signals as a very basic method of hooking into the task lifecycle. Whether for task chaining or additional monitoring.

Notably, signals benefit from the existing exception handling, meaning the user doesn't need to work that out for themselves.

@RealOrangeOne RealOrangeOne added the tasks-api Issues relating to the tasks API and general API contract from the library label Aug 23, 2024
@RealOrangeOne RealOrangeOne force-pushed the feature/signals branch 2 times, most recently from 57f7ce7 to bb55249 Compare August 30, 2024 13:36
@RealOrangeOne RealOrangeOne marked this pull request as ready for review August 30, 2024 13:49
@RealOrangeOne RealOrangeOne force-pushed the feature/signals branch 2 times, most recently from 2d5f481 to 5552edf Compare September 13, 2024 13:10
The global ones can be used, and restored later if needed. The implementation is a bit of a bodge
@RealOrangeOne
Copy link
Owner Author

This PR got a little out of hand, so I extracted the useful features and merged them manually.

@RealOrangeOne RealOrangeOne deleted the feature/signals branch September 13, 2024 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tasks-api Issues relating to the tasks API and general API contract from the library
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant