opened
lucendio
username_0
**What version of ESLint are you using?**
2.2.0

**What configuration and parser (Espree, Babel-ESLint, etc.) are you using?**
Espree

**What did you do? Please include the actual source code causing the issue.**

ESLint config excerpt:
```yaml
no-shadow: [
    2,
    {
        builtinGlobals: true,
        hoist: 'functions',
        allow: []
    }
]
```
js file content:
```js
const path = '/account/:name';
let name = 'unimportant value';
```

**What did you expect to happen?**
variable declaration of ``name``(line:2) doesnt get marked as a problem

**What actually happened? Please include the actual, raw output from ESLint.**
variable declaration of ``name``(line:2) gets marked as a problem

 My guess: regex for finding a previous usage needs a bit more work
[rule: no-shadow] false positive caused by a path string
issue
created
gyandeeps
username_1
variable declaration of name(line:2) gets marked as a problem

Currently your expect vs happened response seems to contradict each other.
comment
created
lucendio
username_0
I am sorry. my mistake. I added the output mesage
comment
created
platinumazure
username_2
You should show your whole config- it's possible an environment is enabling a global called name.
comment
created
lucendio
username_0
[eslintrc.txt](https://github.com/eslint/eslint/files/153847/eslintrc.txt)
NOTE: its a ``.yml`` file, but unfortunately github does not support uploading such extension. so I had to rename it.
I thin you might be right, because renaming both, ``:name`` string (line:1) and variable name preventing the error
comment
created
mysticatea
username_3
The `name` variable is defined in the global of `browser` environment.
So this is correct behavior.
comment
created
faceleg
username_4
Closing as not a bug.
comment
closed
faceleg
username_4
issue
created
lucendio
username_0
thanks for clearing this up. I am sorry for causing extra work.
comment
created
faceleg
username_4
No problem, there are a few of us here whose role is helping manage issues :)
comment