Skip to content
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

Only show the first parse error #344

Merged
merged 1 commit into from
Aug 13, 2023
Merged

Only show the first parse error #344

merged 1 commit into from
Aug 13, 2023

Conversation

c42f
Copy link
Member

@c42f c42f commented Aug 12, 2023

Parser recovery commonly results in several errors which refer to much the same location in the broken source file and are not useful to the user.

Currently the most useful error is the first one, so this PR trims down error printing to only show that one.

Fixes JuliaLang/julia#50223

Parser recovery commonly results in several errors which refer to much
the same location in the broken source file and are not useful to the
user.

Currently the most useful error is the first one, so this PR trims down
error printing to only show that one.
@codecov
Copy link

codecov bot commented Aug 12, 2023

Codecov Report

Merging #344 (e7669ab) into main (94bad1a) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #344   +/-   ##
=======================================
  Coverage   96.56%   96.56%           
=======================================
  Files          14       14           
  Lines        4158     4161    +3     
=======================================
+ Hits         4015     4018    +3     
  Misses        143      143           
Files Changed Coverage Δ
src/parser_api.jl 94.02% <100.00%> (+0.27%) ⬆️

@c42f c42f merged commit df84e02 into main Aug 13, 2023
32 checks passed
@c42f c42f deleted the caf/only-print-first-error branch August 13, 2023 06:44
c42f added a commit that referenced this pull request Aug 13, 2023
Parser recovery commonly results in several errors which refer to much
the same location in the broken source file and are not useful to the
user.

Currently the most useful error is the first one, so this PR trims down
error printing to only show that one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Excessive number of parser errors displayed
1 participant