From 08f183a6d2b63321a469f4c19545c0ff9ea80195 Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Mon, 20 May 2024 01:58:06 -1000 Subject: [PATCH] Fix broken link in asyncio thread safety docs (#2176) * Fix broken link in asyncio thread safety docs * Fix broken link in asyncio thread safety docs --- docs/asyncio_thread_safety.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/asyncio_thread_safety.md b/docs/asyncio_thread_safety.md index 450ee7bf..209eb09e 100644 --- a/docs/asyncio_thread_safety.md +++ b/docs/asyncio_thread_safety.md @@ -6,7 +6,7 @@ Developing with asyncio requires careful attention to thread safety, as nearly a Home Assistant has some conventions for handling async and non-async code in the same code base. The top highlights are: -- Deciding how to run a function from a helper depends on whether it is decorated with `@callback` to indicate it will not block and is safe to run in the event loop; for more details, see [Working with Async](asyncio_working_with_async). +- Deciding how to run a function from a helper depends on whether it is decorated with `@callback` to indicate it will not block and is safe to run in the event loop; for more details, see [Working with Async](asyncio_working_with_async.md). - Most APIs have a sync and async version when calling a function from a thread. The async APIs are prefixed with `async_`. For example, when firing an event from a thread other than the event loop, use `hass.bus.fire` instead of `hass.bus.async_fire`. :::tip