From 73e96b1def5f650c758d7719958ec0a6e19ae6ec Mon Sep 17 00:00:00 2001 From: Tim Castillo Date: Fri, 10 May 2024 09:29:00 -0400 Subject: [PATCH] Update adding-partitions-to-assets.md --- .../dagster-essentials/lesson-8/adding-partitions-to-assets.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/dagster-university/pages/dagster-essentials/lesson-8/adding-partitions-to-assets.md b/docs/dagster-university/pages/dagster-essentials/lesson-8/adding-partitions-to-assets.md index bfd35e0535f6b..ee982eef1dc65 100644 --- a/docs/dagster-university/pages/dagster-essentials/lesson-8/adding-partitions-to-assets.md +++ b/docs/dagster-university/pages/dagster-essentials/lesson-8/adding-partitions-to-assets.md @@ -43,7 +43,7 @@ To add the partition to the asset: ) ``` -3. In Dagster, the `context` argument provides you with metadata about the current materialization. To access it, include it as the first argument in the asset definition function. You can enable typehinting for this by importing `AssetExecutionContext` from `dagster` and adding it to the function signature. For example, the updated asset definition should look like this: +3. In Dagster, the `context` argument provides you with metadata about the current materialization. To access it, include it as the first argument in the asset definition function. You can enable type hinting for this by importing `AssetExecutionContext` from `dagster` and adding it to the function signature. For example, the updated asset definition should look like this: ```python from dagster import asset, AssetExecutionContext