Event Lifecycle Oriented Hooking
Event Lifecycle Oriented Hooking
Hi HN ! This project is my personal way of implementing a hooking [1] mechanism. It is made from scratch after several disappointing attempts. I designed the hooking mechanism so that its API is both minimalistic and intuitive (at least from my point of view). Since an event [2] has a beginning and an end, I thought it would be cool to be able to specify at what stage of its lifecycle a given hook should be called. So, when binding a hook to an event, I can set that spec which by default is the start of an event. I also introduced the ability to break, from a hook, the execution of an event and also to temporarily freeze a hooking session. The library is written in Python and is available on PyPI [3]. I'd like to know what you think of this project and its API (if we abstract from the underlying implementation language). [1] https://en.wikipedia.org/wiki/Hooking [2] https://en.wikipedia.org/wiki/Event_(computing) [3] https://github.com/pyrustic/hooking#installation
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Incorrect prediction on native model
Similar products
Deigma, an event sampler for Erlang/OTP
'classchange' Event for DOM
An Event Sourced Minesweeper
Ever – a callback-less event reactor for Ruby
A minimalistic async event bus implementation
Webhooks for Any Event
An Introduction to Event Storming and DDD
Mixpanel Event Queueing Wrapper
Create badges for your event
All-inclusive event platform for academia