Nested tasks don't get started unless #children present #744
Description
On Sat, Sep 29, 2012 at 1:05 PM, Denis Kudriashov wrote:
> Hello.
>
> I try build little application with WATasks's. And I find strange
> behaviour.
> When I call some WATask inside another WATask like this:
>
> MyMainTask>>go
> self call: MySubtask new
>
> I got error due to method:
>
> WATask>>renderContentOn: html
> "Tasks define behaviour and should not render themselves directly.
> Behaviour is defined
> in the #go method, which can use #call: and other methods to display
> components.
>
> In general, if this method is called, it means that the application
> has not been configured
> properly to use Flow and the task was never executed."
>
> WATaskNotDelegated signal: 'This task has no delegation.'
>
> Which means that #go method not executed for callable MySubtask (I put
> halt on it).
> Is this known restriction or it is just bug?
>
> Best regards,
> Denis
Original issue reported on code.google.com by [email protected] on 8 Oct 2012 at 6:45