VS Code IntelliSense issues

General Usage
,
1

VS Code extension for Julia provides some nice static checks, e.g. it hints “possibly undeclared variable”, and also allows going to definition. But it seems to work only within one file. Even if I have include, definitions from the included file are not visible. So I got hundreds of “possibly undeclared” variables, which is very annoying.

Is there any workaround for this? Can I make VS Code search definitions in included files, or even better in the whole workspace? If follow the standard package structure, you end up with multiple files that are to be included in one “main” file, and, therefore, these files are not valid on their own.

P.S. There is a “go to symbol in workspace” function, but it doesn’t solve the problem with undeclared variables.

1 Like
2

include’s usually work fine for me. It is important that the includes are “simple” in the sense that they are just "include("folder/file.jl"). More “dynamic” includes like include(joinpath("folder", "file.jl")) will, right now, not work.

3

Ah, I see: includes are processed fine if they contain plain code, without modules. Definitions inside modules, however, cannot be found.

4

I think it would be nice to have something like project file for Julia. Or maybe even consider some julia file as a project file. As packages usually have one main file, which has a bunch of includes, it could be used to deduce the order in which files’ contents should be analyzed.

5

If you define a new module inside a file and include that file, you need to explicitly import the variables in that module to get access to them. So perhaps this is not a vscode error?

That is in fact how it (should) work. For a package, Package.jl, the src/Package.jl file is considered the “top file” and from there, includes are processed.

6

I have exports in the included module and using in the file that includes. Here is an example.

file1.jl

module GraphAux

export Vertex

struct Vertex{T}
    data :: T
end

end

file2.jl

include("file1.jl")

using GraphAux

struct Graph{T}
    vertices :: Vector{Vertex{T}}
    
end

VS Code cannot find the definition of Vertex in file2.jl.

Do I need to specify some workspace settings maybe?

7

Interesting, if I do import GraphAux: Vertex it can find it. This seems like a bug in LanguageServer.jl.

8

Hi all,
There are issues w/ scoping and variables exported from user defined modules, they’ve not worked for a while but will be fixed when StaticLint gets integrated (next vscode release)

2 Likes
9

Ah, sounds promising, thank you!

And as for the package structure: when I edit a source file file3.jl that is included into a “top file” of a package but does not include anything itself, would the VS Code look for definitions from files file1.jl and file2.jl included into the top file before file3.jl?

10

Hi all,

I have a (possibly related) issue with VS code intellisense. I’m only just transitioning from Juno/Atom into Julia_extension/VSCode, and still getting used to it.

When I create some kind of data structure in Julia, e.g. load a CSV file as a dataframe or create a NamedTuple, I don’t get a list of fields upon using “.”.

Example:

df = DataFrame!(CSV.File(“data/mydatafile.csv”))

In Juno “df.” automatically gives a list of column headings to choose from, but Julia_extension to VScode isn’t doing this. Is this a configuration problem?

I’m using Julia 1.3 on a Mac OSX 10.15.

11

No, simply not implemented yet. #1507 will fix it though.

1 Like
12

Thanks for the very swift reply.

Wish I was more skilled and could pitch in! But I’m a scientist who is loving Julia as a tool rather than a skilled code craftsman.

13

FWIW, I noticed issues like this (undeclared and missing type definitions) after doing some code reorganization by moving type declarations into separate file. I was using Revise and tests kept working fine in my active session (:tada:), but vscode-julia intellisense added many squigglies. Restarting VSCode fixed these, so I suppose there was some language server cache which did not clear until the restart.