This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
Fix proselint timeout by copying 60 seconds hard limit and uniqueKey from linter-bootlint … #86
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…and added null check for results
This is a fix for linter-proselint timeouts that occur linting large files with thousands or ten of thousands of lines, originally identified in #4
Copied a fix from linter-bootlint that added a 60 seconds hard limit to the linting process. Error identified here: AtomLinter/linter-bootlint#44
Also, identified a problem caused by sequential linting requests being invoked before the preceding linting has completed causing the linter to return a null. Caused by CTRL+S saving forced a re-lint before the previous request is finished. Fix is to ignore subsequent lint requests and dummy in a non-null return value.
@Arcanemagus