Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Invalid position given by 'W116' #432

Open
fkiefl opened this issue Jun 28, 2017 · 6 comments
Open

Invalid position given by 'W116' #432

fkiefl opened this issue Jun 28, 2017 · 6 comments
Labels

Comments

@fkiefl
Copy link

fkiefl commented Jun 28, 2017

JSHint returned a point that did not exist in the document being edited.
Rule: W116
Requested start point: 45:35

Debug information:

Atom version: 1.18.0
linter-jshint version: v3.1.4
JSHint version: jshint v2.9.5
Hours since last Atom restart: 0
Platform: win32
Current file's scopes: [
  "source.js",
  "meta.function-call.js",
  "meta.arguments.js",
  "meta.switch-statement.js",
  "punctuation.definition.section.case-statement.js"
]
linter-jshint configuration: {
  "executablePath": "",
  "lintInlineJavaScript": false,
  "disableWhenNoJshintrcFileInPath": false,
  "scopes": [
    "source.js",
    "source.js-semantic"
  ],
  "jshintFileName": ".jshintrc",
  "jshintignoreFilename": ".jshintignore"
}

jshintrc config
"predef" : ["define","requirejs","require","module"]

@Arcanemagus
Copy link
Member

Is your file indented using tabs?

@luop90
Copy link

luop90 commented Jul 17, 2017

I'm getting the same error, and yes, indented using tabs.

@fkiefl
Copy link
Author

fkiefl commented Jul 17, 2017

yes the same in my config using indented using tabs

@Arcanemagus
Copy link
Member

Okay, this is definitely jshint/jshint#3151 then, please follow that issue for when this will get resolved in JSHint.

If anyone is directed here and isn't using tabs to indent your file please file a new issue with a file to reproduce it on the JSHint repo, or file one here and I'll try to help you in getting one filed there where it can be fixed.

@Arcanemagus
Copy link
Member

There are reports that if you set your indent property of your JSHint configuration to 1 this issue can be worked around. If you don't have a .jshintrc file the following should work:

{
  "indent": 1
}

@fkiefl
Copy link
Author

fkiefl commented Sep 14, 2017 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants