Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
step.while() no longer working
See original GitHub issueI’m using the latest Element as from today 1.3.8 (yarn global upgrade element-cli)
step.while() runs once but does not repeat
Reproducible even using the example code from Github:
https://github.com/flood-io/element/blob/master/examples/condition/test.ts
element run test.ts
+62s info: ===> Step 'Step 5'
Step 5
+62s info: ---> Step 'Step 5' finished in 1ms
The text “Step 5” should be output 3 times from the example code, but it’s only output once.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How to run a github-actions step, even if the previous ...
Causes the step to always execute, and returns true, even when canceled. A job or step will not run when a critical failure...
Read more >Loops: while and for
Any expression or variable can be a loop condition, not just comparisons: the condition is evaluated and converted to a boolean by while...
Read more >Loops: while(), for() and do .. while() - Physics and Astronomy
The while() loop repeats as long as the condition is true (non-zero). If the condition is false the body of the loop never...
Read more >while - JavaScript - MDN Web Docs - Mozilla
The while statement creates a loop that executes a specified statement as long as the test condition evaluates to true. The condition is ......
Read more >C Programming Course Notes - Looping Constructs
While loops check for the stopping condition first, and may not execute the body ... the body of the loop, and is no...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @cjpablo92, we plan to release a fix in version 1.4. But this issue has been fixed in the latest element beta.
What’s the status of this fix? I’m using 2.0.4 and still getting this behaviour.
I found #333 but can’t see any sign of it in
betaorcanary