From d6a7e075a794c7345fa1b5e4fc5c7498f8c384e1 Mon Sep 17 00:00:00 2001 From: Haomin Shi Date: Sun, 2 Jul 2023 12:17:09 -0400 Subject: [PATCH] fix: should be TodoListWorkflow.State instead of TodoWorkflow.State --- samples/tutorial/Tutorial4.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/samples/tutorial/Tutorial4.md b/samples/tutorial/Tutorial4.md index 1cb8131e0..d4b64c1ed 100644 --- a/samples/tutorial/Tutorial4.md +++ b/samples/tutorial/Tutorial4.md @@ -151,7 +151,7 @@ object TodoWorkflow : StatefulWorkflow>() { } ``` -Because `TodoWorkflow.State` has no properties anymore, it can't be a `data` class, so we need to change it to an `object`. Since the only reason to have a custom type for state is to define the data we want to store, we don't need a custom type anymore so we can just use `Unit`. You might ask why we need a state at all now. We will discuss that in the next section. For now `Unit` will get us moving forward. +Because `TodoListWorkflow.State` has no properties anymore, it can't be a `data` class, so we need to change it to an `object`. Since the only reason to have a custom type for state is to define the data we want to store, we don't need a custom type anymore so we can just use `Unit`. You might ask why we need a state at all now. We will discuss that in the next section. For now `Unit` will get us moving forward. ```kotlin object TodoListWorkflow : StatefulWorkflow() {