type hint fix

Author: krylosov-aa

context_async_sqlalchemy/test_utils.py

@@ -28,7 +28,9 @@ async def rollback_session(
 
 
 @asynccontextmanager
-async def set_test_context(auto_close: bool = False) -> AsyncGenerator[None]:
+async def set_test_context(
+    auto_close: bool = False,
+) -> AsyncGenerator[None, None]:
     """
     Opens a context similar to middleware.
 
@@ -56,7 +58,7 @@ async def set_test_context(auto_close: bool = False) -> AsyncGenerator[None]:
 async def put_savepoint_session_in_ctx(
     connection: DBConnect,
     session: AsyncSession,
-) -> AsyncGenerator[None]:
+) -> AsyncGenerator[None, None]:
     """
     Sets the context to a session that uses a save point instead of creating
         a transaction. You need to pass the session you're using inside

docs/api/index.html

@@ -387,7 +387,7 @@ <h3 id="rollback_session">rollback_session</h3>
 <hr />
 <h3 id="set_test_context">set_test_context</h3>
 <pre><code class="language-python">@asynccontextmanager
-async def set_test_context(auto_close: bool = False) -&gt; AsyncGenerator[None]:
+async def set_test_context(auto_close: bool = False) -&gt; AsyncGenerator[None, None]:
 </code></pre>
 <p>A context manager that creates a new context in which you can place a
 dedicated test session.
@@ -403,7 +403,7 @@ <h3 id="put_savepoint_session_in_ctx">put_savepoint_session_in_ctx</h3>
 <pre><code class="language-python">async def put_savepoint_session_in_ctx(
     connection: DBConnect,
     session: AsyncSession,
-) -&gt; AsyncGenerator[None]:
+) -&gt; AsyncGenerator[None, None]:
 </code></pre>
 <p>Sets the context to a session that uses a save point instead of creating
         a transaction. You need to pass the session you're using inside

docs/search/search_index.json

@@ -173,7 +173,7 @@ <h2 id="override-context">Override context</h2>
 @pytest_asyncio.fixture(autouse=True)
 async def db_session_override(
     db_session_test: AsyncSession,
-) -&gt; AsyncGenerator[None]:
+) -&gt; AsyncGenerator[None, None]:
     &quot;&quot;&quot;
     The key thing about these tests is that we override the context in advance.
     The middleware has a special check that won't initialize the context

docs/testing/index.html

@@ -317,7 +317,7 @@ It’s intended for use in fixtures to execute SQL queries during tests.
 ### set_test_context
 ```python
 @asynccontextmanager
-async def set_test_context(auto_close: bool = False) -> AsyncGenerator[None]:
+async def set_test_context(auto_close: bool = False) -> AsyncGenerator[None, None]:
 ```
 A context manager that creates a new context in which you can place a
 dedicated test session.
@@ -338,7 +338,7 @@ active, and you want all sessions to be closed automatically.
 async def put_savepoint_session_in_ctx(
     connection: DBConnect,
     session: AsyncSession,
-) -> AsyncGenerator[None]:
+) -> AsyncGenerator[None, None]:
 ```
 Sets the context to a session that uses a save point instead of creating
         a transaction. You need to pass the session you're using inside

docs_sources/docs/api.md

@@ -90,7 +90,7 @@ from context_async_sqlalchemy.test_utils import (
 @pytest_asyncio.fixture(autouse=True)
 async def db_session_override(
     db_session_test: AsyncSession,
-) -> AsyncGenerator[None]:
+) -> AsyncGenerator[None, None]:
     """
     The key thing about these tests is that we override the context in advance.
     The middleware has a special check that won't initialize the context

docs_sources/docs/testing.md

@@ -22,7 +22,7 @@
 @pytest_asyncio.fixture(autouse=True)
 async def cleanup_tables_after(
     app: FastAPI,  # To make the connection to the database in lifespan
-) -> AsyncGenerator[None]:
+) -> AsyncGenerator[None, None]:
     """
     After each test, we delete all data from the tables to isolate the data.
     We always clear the data after each test to avoid interfering with

examples/fastapi_example/tests/non_transactional/conftest.py

@@ -25,7 +25,7 @@
 @pytest_asyncio.fixture(autouse=True)
 async def db_session_override(
     db_session_test: AsyncSession,
-) -> AsyncGenerator[None]:
+) -> AsyncGenerator[None, None]:
     """
     The key thing about these tests is that we override the context in advance.
     The middleware has a special check that won't initialize the context

examples/fastapi_example/tests/transactional/conftest.py

@@ -22,7 +22,7 @@
 @pytest_asyncio.fixture(autouse=True)
 async def cleanup_tables_after(
     app: FastAPI,  # To make the connection to the database in lifespan
-) -> AsyncGenerator[None]:
+) -> AsyncGenerator[None, None]:
     """
     After each test, we delete all data from the tables to isolate the data.
     We always clear the data after each test to avoid interfering with

examples/fastapi_with_pure_asgi_example/tests/non_transactional/conftest.py

@@ -25,7 +25,7 @@
 @pytest_asyncio.fixture(autouse=True)
 async def db_session_override(
     db_session_test: AsyncSession,
-) -> AsyncGenerator[None]:
+) -> AsyncGenerator[None, None]:
     """
     The key thing about these tests is that we override the context in advance.
     The middleware has a special check that won't initialize the context