Why Condition.Precede do not use len(cond.mapper) instead of i

[Tangxinqi]

Why doesn't the first for loop in the task.precede method use len(cond.mapper) instead of i? This way, for a ConditionTask, precede could be executed multiple times. Otherwise, if precede is incorrectly executed multiple times, the final flow execution might not achieve the intended design

[noneback]

That makes sense. Can you make a PR for this?

[Tangxinqi]

That makes sense. Can you make a PR for this?

ok,let me try

[Tangxinqi]

That makes sense. Can you make a PR for this?

sorry, I do not have permission to push branch to remote, please grant permission for me

[noneback]

That makes sense. Can you make a PR for this?

sorry, I do not have permission to push branch to remote, please grant permission for me

You don't need permissions to make a pr.

https://github.com/firstcontributions/first-contributions, here is a tutorial about how to make contributions to open source repo.

Basically, you need to fork this repo and push to your own forked repo and make a pull request in the original repo.

[Tangxinqi]

That makes sense. Can you make a PR for this?

sorry, I do not have permission to push branch to remote, please grant permission for me

You don't need permissions to make a pr.

https://github.com/firstcontributions/first-contributions, here is a tutorial about how to make contributions to open source repo.

Basically, you need to fork this repo and push to your own forked repo and make a pull request in the original repo.

thanks for reply, here is my pr #103

[noneback]

#103