New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix for-await printing #5322
Fix for-await printing #5322
Conversation
Only the first for-await was correctly printed all subsequent for-await statements where printed as for-of as the variable op was changed inside the buildForXStatement
@danez, thanks for your PR! By analyzing the history of the files in this pull request, we identified @loganfsmyth, @hzoo and @erikdesjardins to be potential reviewers. |
@@ -18,11 +18,11 @@ async function a() { | |||
for ({ a } in {}) {} | |||
for ({ a } of []) {} | |||
async function a() { | |||
for ({ a } of []) {} | |||
for await ({ a } of []) {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sad that I didn't catch this before
Codecov Report
@@ Coverage Diff @@
## master #5322 +/- ##
==========================================
- Coverage 89.44% 89.44% -0.01%
==========================================
Files 204 204
Lines 9950 9949 -1
Branches 2688 2689 +1
==========================================
- Hits 8900 8899 -1
Misses 1050 1050
Continue to review full report at Codecov.
|
Only the first for-await was correctly printed all subsequent for-await statements where printed as for-of as the variable op was changed inside the buildForXStatement
Only the first for-await was correctly re-printed as for-await all subsequent for-await statements
where printed as for-of as the variable op was changed inside the buildForXStatement during the first run.