[Feature-Request/Question] Hide diagnostics while keeping require definitions for project files

[sewbacca]

I have a project, where I use luarocks with modules directly installed in the projects folder (similar to how npm does it), which is handy for adding require paths, however what should I do, if they raise warnings?

I tried the following:

{
	"Lua.runtime.version": "LuaJIT",
	"Lua.workspace.library": [
		"${3rd}/love2d/library",
		"${3rd}/lfs/library",
		"${workspaceFolder}/lua_modules"
	],
	"Lua.runtime.path": [
		"src/?.lua",
		"src/?/init.lua",
		"doc/?.lua",
		"${workspaceFolder}/share/lua/5.1/?.lua",
		"${workspaceFolder}/share/lua/5.1/?/init.lua"
	],
	"Lua.workspace.ignoreDir": [
		"extern",
		"lua_modules" // Need option to ignore diagnostics, but keep definitions
	],
	"Lua.diagnostics.libraryFiles": "Disable",
}

[sumneko]

You should change Lua.workspace.library to lua_modules instead of ${workspaceFolder}/lua_modules .

[sewbacca]

I don't understand what I am doing wrong.

{
	"Lua.runtime.version": "LuaJIT",
	"Lua.workspace.library": [
		"${3rd}/love2d/library",
		"${3rd}/lfs/library",
		"lua_modules"
	],
	"Lua.runtime.path": [
		"src/?.lua",
		"src/?/init.lua",
		"doc/?.lua",
		"${workspaceFolder}/lua_modules/share/lua/5.1/?.lua",
		"${workspaceFolder}/lua_modules/share/lua/5.1/?/init.lua"
	],
	"Lua.workspace.ignoreDir": [
		"extern",
		// "lua_modules"
	],
	"Lua.diagnostics.libraryFiles": "Disable",
	"Lua.workspace.checkThirdParty": false,
}

with Lua.workspace.ignoreDir I get no require recommendations, and without it I get the warnings.

[sumneko]

It works for me

[sewbacca]

Ah I've got it.
First I tested it a bit wrong, I forgot that currently I was only using c libraries. I created a test file in "${workspaceFolder}/lua_modules/share/lua/5.1/?.lua", but now it seemed to me it was correct, yet still no completion.
The issue was, that not only in Lua.workspace.library, but also in Lua.runtime.path you shouldn't use ${workspaceFolder}.
Thanks for your help.

[carsakiller]

Hello @sewbacca! Has your issue been resolved?

[sewbacca]

Yes, but I didn't close the issue, since I didn't know whether or not absolute paths into the working Folder should be allowed.

The issue was, that not only in Lua.workspace.library, but also in Lua.runtime.path you shouldn't use ${workspaceFolder}.