Question, perhaps a bug, on inline source implementation: global
vs globals
#12128
Labels
archived due to age
This issue has been archived; please open a new issue for any further discussion
documentation
Relates to ESLint's documentation
question
This issue asks a question about ESLint
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using?
Please show your full configuration:
Configuration
n/a and defaults in packages
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
/* global someGlobal */
vs.
/* globals someGlobal */
n/a
What did you expect to happen?
Trying to develop some consistency between all the linters to code against. I have noticed that ESLint doesn't seem to care on pluralization as do other linters (could be wrong but this is what some packages, extensions, and add-ons seem to be doing quietly for compatibility).
What actually happened? Please include the actual, raw output from ESLint.
When using either
global
orglobals
inline comments in source the warning triangles go away in those packages, extensions, and/or add-ons.Appreciate the clarity here on which one to use for ESLint so we can know what to expect (i.e. best practice as the docs have). 😄
The text was updated successfully, but these errors were encountered: