You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Include LuaCATS library with a dependent extension #127
I would like to create a simple VSCode extension which depends upon sumneko.lua and bundles those types. Is this possible?
If it is not currently possible, I believe vscode-lua could provide a public API for other extensions by adding additional functions to the object returned from the activate(context: vscode.ExtensionContext) function:
This exported API could be something simple like library_add(path) so I can provide a path to a subdirectory in my extension bundle for my lua ---@meta files.
I would love to attempt this myself, but I'm still struggling setup a working extension development environment. See: #125.
The intention with addons is that the language server can support definitions like this so that you don't have to make your own VS Code extension and it can be used in other editors as well. You could configure your addon for "automatic" enabling using a config.json to make things a little easier.
You could also add this to LLS-Addons which can then be used by the addon manager in VS Code – however, reading their license makes me think that maybe they would not like that.
Currently, my concern is that managing addons and installing them is quickly turning into a full-blown package manager.
Activity
[-]Possible to bundle LuaCATS library with extension[/-][+]Include LuaCATS library with a dependent extension[/+]carsakiller commentedon Oct 23, 2023
The intention with addons is that the language server can support definitions like this so that you don't have to make your own VS Code extension and it can be used in other editors as well. You could configure your addon for "automatic" enabling using a
config.jsonto make things a little easier.You could also add this to LLS-Addons which can then be used by the addon manager in VS Code – however, reading their license makes me think that maybe they would not like that.
Currently, my concern is that managing addons and installing them is quickly turning into a full-blown package manager.