nigelrook / vscode-linter-erlc Goto Github PK

Currently, .hrl files get linted as if they were .erl files. As a minimum, this causes a module name warning.

Minimally: Don't lint .hrl files
Ideally: Lint .hrl files in a way that generates appropriate warnings/errors only

Kerl makes it possible to switch between erlang versions.

See: https://github.com/kerl/kerl

When one uses kerl there is no direct erlc executable path. You first have to activate a build before you can use it.

Is it possible to support this?

see https://code.visualstudio.com/updates/June_2016#_creating-errorswarnings-from-an-extension-diagnostics

I have a project with modules that have -compile(export_all).
I want to disable the warning for export_all.

I tried to change "erlang.linter-erlc.executablePath" from "erlc" to "erlc +nowarn_export_all" but that did not work. Any ideas?

If the contents of a .hrl file generates a warning or error, then a file including that .hrl currently shows a warning/error against whatever line of the .hrl contains the error (ie. if x.hrl warns at line 15, and y.erl includes x, then y.erl will show the warning from x.hrl at line 15).

Minimally: Suppress warnings/errors from headers in including files
Ideally: Warnings/errors from headers should show on the -include line