Describe the bug
When using nextBlockId in js code blocks, it seems to execute the block after the specified block rather than the specified block itself.
To Reproduce
I set up 3 js code blocks. Js0 is the executed block, and in js0 I haveautomaNextBlock(null, {nextBlockId: 'myv7fq5'}), where 'myv7fq5' is the id of js1.
Expected behavior
I was expecting js1 to execute, but instead js2 executed. Is this a bug or feature?
Screenshots
Desktop (please complete the following information):
a24ac1
commented
7 months ago
Describe the bug When using nextBlockId in js code blocks, it seems to execute the block after the specified block rather than the specified block itself.
To Reproduce I set up 3 js code blocks. Js0 is the executed block, and in js0 I have
automaNextBlock(null, {nextBlockId: 'myv7fq5'}), where 'myv7fq5' is the id of js1.Expected behavior I was expecting js1 to execute, but instead js2 executed. Is this a bug or feature?
Screenshots
Desktop (please complete the following information):