This is an automated email from the ASF dual-hosted git repository. joshfell pushed a commit to branch josh-fell-patch-1 in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 773f21d95e3f3281f9d4ddfb4e3280c7553a1006 Author: Josh Fell <48934154+josh-f...@users.noreply.github.com> AuthorDate: Tue Feb 21 15:36:17 2023 -0500 FIx formatting of Dataset inlet/outlet note in TaskFlow concepts --- docs/apache-airflow/core-concepts/taskflow.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/apache-airflow/core-concepts/taskflow.rst b/docs/apache-airflow/core-concepts/taskflow.rst index 92daf5dd5c..6f46cdb4cd 100644 --- a/docs/apache-airflow/core-concepts/taskflow.rst +++ b/docs/apache-airflow/core-concepts/taskflow.rst @@ -91,9 +91,10 @@ need to be able to be serialized. Airflow out of the box supports all built-in t supports objects that are decorated with ``@dataclass`` or ``@attr.define``. The following example shows the use of a ``Dataset``, which is ``@attr.define`` decorated, together with TaskFlow. -:: +.. note:: + + An additional benefit of using ``Dataset`` is that it automatically registers as an ``inlet`` in case it is used as an input argument. It also auto registers as an ``outlet`` if the return value of your task is a ``dataset`` or a ``list[Dataset]]``. - Note: An additional benefit of using ``Dataset`` is that it automatically registers as an ``inlet`` in case it is used as an input argument. It also auto registers as an ``outlet`` if the return value of your task is a ``dataset`` or a ``list[Dataset]]``. .. code-block:: python