Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Docs: Mention the globals key in the no-undef docs #9867

Merged
merged 3 commits into from Jan 22, 2018
Merged

Docs: Mention the globals key in the no-undef docs #9867

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
465a3b0
Mention the `globals` key
dandv Jan 20, 2018
c6d401e
Docs: mention specifying globals
dandv Jan 20, 2018
b43ad39
Docs: mention the globals key in the no-undef Rule Details section
dandv Jan 21, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/rules/no-undef.md
View file
Open in desktop
Expand Up @@ -4,7 +4,7 @@ This rule can help you locate potential ReferenceErrors resulting from misspelli

## Rule Details

Any reference to an undeclared variable causes a warning, unless the variable is explicitly mentioned in a `/*global ...*/` comment.
Any reference to an undeclared variable causes a warning, unless the variable is explicitly mentioned in a `/*global ...*/` comment, or specified in the [`globals` key in the configuration file](https://eslint.org/docs/user-guide/configuring#specifying-globals). A common use case for these is if you intentionally use globals that are defined elsewhere (e.g. in a script sourced from HTML).

Examples of **incorrect** code for this rule:

Expand Down