diff --git a/README.md b/README.md index cfe5442..63daa46 100644 --- a/README.md +++ b/README.md @@ -29,8 +29,8 @@ Supported Python versions - - Code style: black + + Code style: black

diff --git a/docs/index.md b/docs/index.md index 601a573..872161a 100644 --- a/docs/index.md +++ b/docs/index.md @@ -47,8 +47,8 @@ hide: Supported Python versions - - Code style: black + + Code style: black

diff --git a/docs/release-notes.md b/docs/release-notes.md index a00ce62..57f0ff0 100644 --- a/docs/release-notes.md +++ b/docs/release-notes.md @@ -21,7 +21,7 @@ hide: - Removed the base `Event` class due to improved event semantics and unnecessary redundancy. - Renamed the `get_event_registry()` method of `EventLinker` to `get_registry()`. - Renamed the `__event_registry` inner property of `EventLinker` to `__registry`. -- Renamed the `get_events_by_handler()` method of `EventLinker` to `get_event_handlers_by_events()`. +- Renamed the `get_events_by_handler()` method of `EventLinker` to `get_events_by_event_handler()`. - Renamed the `get_handlers_by_events()` method of `EventLinker` to `get_event_handlers_by_events()`. - Renamed the protected method `_executor_callback()` of the `ExecutorEventEmitter` to `_callback()`. - Renamed the task name of `CeleryEventEmitter` from `_executor` to `pyventus_executor` to avoid collisions with other diff --git a/docs/tutorials/emitters/asyncio/index.md b/docs/tutorials/emitters/asyncio/index.md index 9342326..3eecd43 100644 --- a/docs/tutorials/emitters/asyncio/index.md +++ b/docs/tutorials/emitters/asyncio/index.md @@ -1,8 +1,5 @@ # AsyncIO Event Emitter -!!! warning "🏗️ Work in Progress" - This page is a work in progress. -

  Now that we've covered the base `EventEmitter` interface, let's examine one of its official implementations: the `AsyncIOEventEmitter`. diff --git a/docs/tutorials/emitters/celery/index.md b/docs/tutorials/emitters/celery/index.md index 55aea66..311838b 100644 --- a/docs/tutorials/emitters/celery/index.md +++ b/docs/tutorials/emitters/celery/index.md @@ -1,8 +1,5 @@ # Celery Event Emitter -!!! warning "🏗️ Work in Progress" - This page is a work in progress. -

  The `CeleryEventEmitter` provides a powerful way to build event-driven applications that can handle high volumes of work in a scalable and asynchronous manner. diff --git a/docs/tutorials/emitters/executor/index.md b/docs/tutorials/emitters/executor/index.md index 210607f..baaec51 100644 --- a/docs/tutorials/emitters/executor/index.md +++ b/docs/tutorials/emitters/executor/index.md @@ -1,8 +1,5 @@ # Executor Event Emitter -!!! warning "🏗️ Work in Progress" - This page is a work in progress. -

  The `ExecutorEventEmitter` leverages Python's `concurrent.futures` module to asynchronously execute event emissions across threads or processes. This approach helps optimize performance for applications with diff --git a/docs/tutorials/emitters/fastapi/index.md b/docs/tutorials/emitters/fastapi/index.md index ce57cc2..c37f7c9 100644 --- a/docs/tutorials/emitters/fastapi/index.md +++ b/docs/tutorials/emitters/fastapi/index.md @@ -1,8 +1,5 @@ # FastAPI Event Emitter -!!! warning "🏗️ Work in Progress" - This page is a work in progress. -

  The `FastAPIEventEmitter` provides a powerful way to build reactive [FastAPI](https://fastapi.tiangolo.com/) applications using an event-driven architecture. It leverages FastAPI's asynchronous [BackgroundTasks](https://fastapi.tiangolo.com/reference/background/) diff --git a/docs/tutorials/emitters/index.md b/docs/tutorials/emitters/index.md index 58015fb..644e907 100644 --- a/docs/tutorials/emitters/index.md +++ b/docs/tutorials/emitters/index.md @@ -1,8 +1,5 @@ # Master the Event Emitter -!!! warning "🏗️ Work in Progress" - This page is a work in progress. -

  In the previous tutorial, we learned how to link events with their event handlers using the `EventLinker`. Now, let's dive into the process of dispatching events and triggering the associated callbacks. diff --git a/docs/tutorials/emitters/rq/index.md b/docs/tutorials/emitters/rq/index.md index db890cc..7af1c06 100644 --- a/docs/tutorials/emitters/rq/index.md +++ b/docs/tutorials/emitters/rq/index.md @@ -1,8 +1,5 @@ # RQ Event Emitter -!!! warning "🏗️ Work in Progress" - This page is a work in progress. -

  In the previous sections, we explored different event emitters, such as `AsyncIOEventEmitter` and `ExecutorEventEmitter`. Now, let's dive into the `RQEventEmitter`, a powerful tool for handling events that diff --git a/docs/tutorials/event-linker.md b/docs/tutorials/event-linker.md index 84f9fdb..ce41b28 100644 --- a/docs/tutorials/event-linker.md +++ b/docs/tutorials/event-linker.md @@ -1,8 +1,5 @@ # The EventLinker Registry -!!! warning "🏗️ Work in Progress" - This page is a work in progress. -

  Events are essential for building reactive applications with Pyventus. However, we need a way to connect events to the code that should run in response. This is where the `EventLinker` comes in. diff --git a/docs/tutorials/event.md b/docs/tutorials/event.md index 05af990..f2bc965 100644 --- a/docs/tutorials/event.md +++ b/docs/tutorials/event.md @@ -1,8 +1,5 @@ # Exploring Event Types -!!! warning "🏗️ Work in Progress" - This page is a work in progress. -

  In this first tutorial, you'll learn about defining and handling events in Pyventus. Whether you're new to event-driven programming or just getting started with the package, this guide will explain the key concepts.