Replies: 2 comments 1 reply
-
Hi @DanSava thanks for taking the time to write this up! Unfortunately, I'm not sure there's an easy way to fix this warning. I'll do a little more digging and open a GitHub issue if a solution makes sense. Generally, we recommend initializing tasks outside the flow for readability and clarity on initializing vs. calling tasks. This warning was added to help users that get stuck and is safe to ignore. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Thank you for taking the time to replay and looking into it! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I understand from the documentation you are not supposed to instantiate Tasks inside a flow without using them but in the example:
In my opinion, both instances of the AddTask class are called inside the flow but I still get the following warning:
Is this the intended behaviour?
Beta Was this translation helpful? Give feedback.
All reactions