properly link to ASYNC122

jakkdl · jakkdl · commit 9961abcef5a6 · 2024-09-19T13:03:27.000+02:00
diff --git a/newsfragments/2512.breaking.rst b/newsfragments/2512.breaking.rst
@@ -1,2 +1,2 @@
 :func:`trio.move_on_after` and :func:`trio.fail_after` previously set the deadline relative to initialization time, instead of more intuitively upon entering the context manager. This might change timeouts if a program relied on this behavior. If you want to restore previous behavior you should instead use ``trio.move_on_at(trio.current_time() + ...)``.
-flake8-async has a new rule to catch this, in case you're supporting older trio versions. See :ref:`ASYNC121` (TODO: except it will be ASYNC122, I'm just making sure intersphinx work)
+flake8-async has a new rule to catch this, in case you're supporting older trio versions. See :ref:`ASYNC122`.

Original file line number	Diff line number	Diff line change
`@@ -1,2 +1,2 @@`
`1`	`1`	:func:`trio.move_on_after` and :func:`trio.fail_after` previously set the deadline relative to initialization time, instead of more intuitively upon entering the context manager. This might change timeouts if a program relied on this behavior. If you want to restore previous behavior you should instead use ``trio.move_on_at(trio.current_time() + ...)``.
`2`		-flake8-async has a new rule to catch this, in case you're supporting older trio versions. See :ref:`ASYNC121` (TODO: except it will be ASYNC122, I'm just making sure intersphinx work)
	`2`	+flake8-async has a new rule to catch this, in case you're supporting older trio versions. See :ref:`ASYNC122`.