github/javascript
1
1
Fork 0
mirror of https://github.com/airbnb/javascript.git synced 2026-01-10 03:37:57 -05:00
Code Issues Packages Projects Releases Wiki Activity

[readme] correct no-use-before-define justification

Browse Source 
The recommendation is to declare the variables, classes and functions before. So the contrasting negative example should say after.
This commit is contained in:
hamzahuda
2023-08-12 12:19:30 +01:00
committed by Jordan Harband
parent cda44dad40
commit cb191776db
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -1964,7 +1964,7 @@ Other Style Guides
<a name="no-use-before-define"></a>
- [14.5](#no-use-before-define) Variables, classes, and functions should be defined before they can be used. eslint: [`no-use-before-define`](https://eslint.org/docs/latest/rules/no-use-before-define)
> Why? When variables, classes, or functions are declared before being used, it can harm readability since a reader won't know what a thing that's referenced is. It's much clearer for a reader to first encounter the source of a thing (whether imported from another module, or defined in the file) before encountering a use of the thing.
> Why? When variables, classes, or functions are declared after being used, it can harm readability since a reader won't know what a thing that's referenced is. It's much clearer for a reader to first encounter the source of a thing (whether imported from another module, or defined in the file) before encountering a use of the thing.
```javascript
// bad