From 3200f44d1dcbb83ed620b556e57bde70b942cc02 Mon Sep 17 00:00:00 2001 From: colton Date: Fri, 20 Dec 2024 13:55:03 -0500 Subject: [PATCH] Update docs/docs-beta/docs/tutorial/multi-asset-integration.md Co-authored-by: Nikki Everett --- docs/docs-beta/docs/tutorial/multi-asset-integration.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/docs-beta/docs/tutorial/multi-asset-integration.md b/docs/docs-beta/docs/tutorial/multi-asset-integration.md index 0990291a2c4d3..d5dc7f91c26a7 100644 --- a/docs/docs-beta/docs/tutorial/multi-asset-integration.md +++ b/docs/docs-beta/docs/tutorial/multi-asset-integration.md @@ -203,7 +203,11 @@ class ReplicationTranslator: return AssetKey(str(table_definition.get("name"))) ``` -Next, we'll update `custom_replication_assets` to use the translator when defining the `key` on the `AssetSpec`. **Note** that we took this opportunity to also include the replication project and translator instance on the `AssetSpec` metadata. This is a workaround that we tend to employ in this approach, as it makes it possible to define these objects once and then access them on the context of our asset. +Next, we'll update `custom_replication_assets` to use the translator when defining the `key` on the `AssetSpec`. + +:::note +Note that we took this opportunity to also include the replication project and translator instance on the `AssetSpec` metadata. This is a workaround that we tend to employ in this approach, as it makes it possible to define these objects once and then access them on the context of our asset. +::: ```python def custom_replication_assets(