mirror of
https://github.com/mozilla/pdf.js.git
synced 2025-04-25 09:38:06 +02:00
Use the ESLint no-restricted-syntax
rule to ensure that assert
is always called with two arguments
Having `assert` calls without a message string isn't very helpful when debugging, and it turns out that it's easy enough to make use of ESLint to enforce better `assert` call-sites. In a couple of cases the `assert` calls were changed to "regular" throwing of errors instead, since that seemed more appropriate. Please find additional details about the ESLint rule at https://eslint.org/docs/rules/no-restricted-syntax
This commit is contained in:
parent
491904d30a
commit
e1f340a0c2
14 changed files with 73 additions and 22 deletions
|
@ -216,7 +216,7 @@ class Parser {
|
|||
} else if (state === 1) {
|
||||
state = ch === I ? 2 : 0;
|
||||
} else {
|
||||
assert(state === 2);
|
||||
assert(state === 2, "findDefaultInlineStreamEnd - invalid state.");
|
||||
if (ch === SPACE || ch === LF || ch === CR) {
|
||||
maybeEIPos = stream.pos;
|
||||
// Let's check that the next `n` bytes are ASCII... just to be sure.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue