# VS-Code Lint error in DataFrame column access

**URL:** https://discourse.julialang.org/t/vs-code-lint-error-in-dataframe-column-access/103366
**Category:** General Usage
**Tags:** dataframes, vscode
**Created:** [August 30, 2023, 12:56pm UTC](https://discourse.julialang.org/t/vs-code-lint-error-in-dataframe-column-access/103366 "2023-08-30T12:56:43Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![ArchieCall](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/archiecall/32/206_2.png) [@ArchieCall](https://discourse.julialang.org/u/ArchieCall)
#### Post date: [August 30, 2023, 12:56pm UTC](https://discourse.julialang.org/t/vs-code-lint-error-in-dataframe-column-access/103366/1 "2023-08-30T12:56:43Z")

</div>

The following code show a lint error in VS-Code:

```julia
using DataFrames
function Mainline()
    df = DataFrame(col_name = 1:3)

    # this line runs but a linter error is displayed for col_name
    var1 = minimum(df.col_name)

    # these lines all run with no linter errors
    var2 = minimum(df."col_name")
    var3 = minimum(df[!,"col_name"])
    var4 = minimum(df[!,:col_name])

    @show(var1, var2, var3, var4)
end
Mainline()

```

Why is the lint error being shown for the var1 line?  
The DataFrames doc says that “var1 = minimum(df.col\_name)” is an allowed access.

This is not a big deal because the code still runs.

---

<div class="post-metadata">

### Author: ![bkamins](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bkamins/32/208538_2.png) [@bkamins](https://discourse.julialang.org/u/bkamins)
#### Post date: [August 30, 2023, 1:04pm UTC](https://discourse.julialang.org/t/vs-code-lint-error-in-dataframe-column-access/103366/2 "2023-08-30T13:04:43Z")

</div>

> [@ArchieCall](#):
>
> df.col\_name

It is allowed, and I would say that this is the most common way to do it.

---

<div class="post-metadata">

### Author: ![nilshg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nilshg/32/2283_2.png) [@nilshg](https://discourse.julialang.org/u/nilshg)
#### Post date: [August 30, 2023, 1:14pm UTC](https://discourse.julialang.org/t/vs-code-lint-error-in-dataframe-column-access/103366/3 "2023-08-30T13:14:55Z")

</div>

The linter isn’t very good at the minute, and has anecdotally become worse with 1.10. See:

> **[Issues · julia-vscode/julia-vscode](https://github.com/julia-vscode/julia-vscode/labels/area-ls-linter)**
>
> Julia extension for Visual Studio Code. Contribute to julia-vscode/julia-vscode development by creating an account on GitHub.

---

<div class="post-metadata">

### Author: ![ArchieCall](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/archiecall/32/206_2.png) [@ArchieCall](https://discourse.julialang.org/u/ArchieCall)
#### Post date: [August 30, 2023, 1:46pm UTC](https://discourse.julialang.org/t/vs-code-lint-error-in-dataframe-column-access/103366/4 "2023-08-30T13:46:42Z")

</div>

Thanks for the update.  
Irrespective of the lint error, VS-Code still rocks!

---

<div class="post-metadata">

### Author: ![nilshg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nilshg/32/2283_2.png) [@nilshg](https://discourse.julialang.org/u/nilshg)
#### Post date: [August 30, 2023, 2:32pm UTC](https://discourse.julialang.org/t/vs-code-lint-error-in-dataframe-column-access/103366/5 "2023-08-30T14:32:33Z")

</div>

You can look at the linter settings in the Julia extension settings to turn off those linter passes which add more noise than useful info.