Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit f6dff0a

Browse filesBrowse files
Trottaddaleax
authored andcommitted
doc: simplify and clarify ReferenceError material in errors.md
"should always be considered" -> "indicate" PR-URL: #34151 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com> Reviewed-By: Christian Clauss <cclauss@me.com> Reviewed-By: Gerhard Stöbich <deb2001-github@yahoo.de> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Andrey Pechkurov <apechkurov@gmail.com>
1 parent e2fff1b commit f6dff0a
Copy full SHA for f6dff0a

File tree

Expand file treeCollapse file tree

1 file changed

+1
-2
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+1
-2
lines changed
Open diff view settings
Collapse file

‎doc/api/errors.md‎

Copy file name to clipboardExpand all lines: doc/api/errors.md
+1-2Lines changed: 1 addition & 2 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -391,8 +391,7 @@ doesNotExist;
391391
```
392392

393393
Unless an application is dynamically generating and running code,
394-
`ReferenceError` instances should always be considered a bug in the code
395-
or its dependencies.
394+
`ReferenceError` instances indicate a bug in the code or its dependencies.
396395

397396
## Class: `SyntaxError`
398397

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.