-
Notifications
You must be signed in to change notification settings - Fork 17
-
Notifications
You must be signed in to change notification settings - Fork 17
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
[Feature] Continue scanning after unhandled errors #946
Comments
like the idea... give me a bit to think on how to make it look "right" |
jackdewinter
added a commit
that referenced
this issue
Jan 20, 2024
jackdewinter
added a commit
that referenced
this issue
Jan 20, 2024
Was released yesterday, should be available for testing. |
closing due to lack of response |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, all.
Currently when scanning multiple documents the scan process exits immediately if it encounters an unhandled error. While we do need to fix errors either in the code or in the document, this stops us from handling linting issues in documents following the one that triggered the error. This could be avoided if broken files are ignored on error, scanning and linting continues to the end of all files and finally we get a list of files with unhandled errors.
This would work similarly to unit test frameworks - they record test failures or code errors but continue running all following tests.
Here is an example trio of files that will trigger the nasty behaviour, leaving
file 3.md
unchecked:Example expected output:
Actual output:
Thank you for your attention!
Best wishes,
Bugzey
The text was updated successfully, but these errors were encountered: