Skip to content
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.

feat: mark errors with "guessed" unknown nodes instead of errors #1789

Merged
merged 12 commits into from Nov 25, 2021

Conversation

ematipico
Copy link
Contributor

@ematipico ematipico commented Nov 16, 2021

Summary

Closes #1759

This PR groups a number of other PRs that were already merged and reviewed. We removed the usage of ERROR in places the parser can't recover and marks nodes as Unknown.

Test Plan

Current CI

@cloudflare-pages
Copy link

cloudflare-pages bot commented Nov 16, 2021

Deploying with  Cloudflare Pages  Cloudflare Pages

Latest commit: 738331b
Status: ✅  Deploy successful!
Preview URL: https://d0c4f8ec.tools-8rn.pages.dev

View logs

@github-actions
Copy link

github-actions bot commented Nov 16, 2021

Test262 comparison coverage results on windows-latest

Test result main count This PR count Difference
Total 17608 17608 0
Passed 16787 16787 0
Failed 820 820 0
Panics 1 1 0
Coverage 95.34% 95.34% 0.00%

@github-actions
Copy link

Test262 comparison coverage results on windows-latest

Test result main count This PR count Difference
Total 17608 17608 0
Passed 16767 16767 0
Failed 840 840 0
Panics 1 1 0
Coverage 95.22% 95.22% 0.00%

@ematipico ematipico force-pushed the feature/unknown-nodes-errors branch 2 times, most recently from 0f599c0 to 4bf12dd Compare November 17, 2021 17:20
@rome rome deleted a comment from github-actions bot Nov 19, 2021
@github-actions
Copy link

github-actions bot commented Nov 19, 2021

Test262 comparison coverage results on ubuntu-latest

Test result main count This PR count Difference
Total 17608 17608 0
Passed 16787 16787 0
Failed 820 820 0
Panics 1 1 0
Coverage 95.34% 95.34% 0.00%

@ematipico ematipico force-pushed the feature/unknown-nodes-errors branch 2 times, most recently from 24629d5 to da8e59a Compare November 22, 2021 12:24
@MichaReiser
Copy link
Contributor

When/What's your plan for merging this PR? Are you planning to make all error recovery changes first?

@ematipico
Copy link
Contributor Author

When/What's your plan for merging this PR? Are you planning to make all error recovery changes first?

My plan is to remove the usage of ERROR and use Unknown nodes instead when recovering. (exception for TypeScript)

There's one more PR (going to open it soon) and after that I think we can merge this PR.

@ematipico ematipico marked this pull request as ready for review November 25, 2021 10:31
Copy link
Contributor

@MichaReiser MichaReiser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ematipico ematipico merged commit 85bd366 into main Nov 25, 2021
@ematipico ematipico deleted the feature/unknown-nodes-errors branch November 25, 2021 10:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Revisit the parse rules and replace the generic Error handler
2 participants