fix imports

cloudflare · Dec 12, 2024 · 01a7ab5 · 01a7ab5
1 parent e213140
commit 01a7ab5
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/src/content/docs/workflows/build/events-and-parameters.mdx b/src/content/docs/workflows/build/events-and-parameters.mdx
@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-import { MetaInfo, Render, Type } from "~/components";
+import { MetaInfo, Render, Type, Type, WranglerConfig, TypeScriptExample } from "~/components";
 
 When a Workflow is triggered, it can receive an optional event. This event can include data that your Workflow can act on, including request details, user data fetched from your database (such as D1 or KV) or from a webhook, or messages from a Queue consumer.
 

diff --git a/src/content/docs/workflows/build/rules-of-workflows.mdx b/src/content/docs/workflows/build/rules-of-workflows.mdx
@@ -5,6 +5,8 @@ sidebar:
   order: 10
 ---
 
+import { WranglerConfig, TypeScriptExample } from "~/components";
+
 A Workflow contains one or more steps. Each step is a self-contained, individually retriable component of a Workflow. Steps may emit (optional) state that allows a Workflow to persist and continue from that step, even if a Workflow fails due to a network or infrastructure issue.
 
 This is a small guidebook on how to build more resilient and correct Workflows.
-Original file line number
+Diff line change
@@ Expand Up / @@ -6,7 +6,7 @@ sidebar: @@
     ---
-    import { MetaInfo, Render, Type } from "~/components";
+    import { MetaInfo, Render, Type, Type, WranglerConfig, TypeScriptExample } from "~/components";
     When a Workflow is triggered, it can receive an optional event. This event can include data that your Workflow can act on, including request details, user data fetched from your database (such as D1 or KV) or from a webhook, or messages from a Queue consumer.
@@ Expand Down @@