Skip to content

Provide annotations without setting up LSP config using command #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
georgiy-belyanin opened this issue Apr 9, 2025 · 1 comment · May be fixed by #14
Open

Provide annotations without setting up LSP config using command #12

georgiy-belyanin opened this issue Apr 9, 2025 · 1 comment · May be fixed by #14

Comments

@georgiy-belyanin
Copy link
Member

Currently the user need to run Tarantool: initialize VS code extension in existing... for annotations to work. For sure, it works not so well as setting up the annotations automatically. When the extension is updated the old paths might break. Also, it's not cool to ask the user to perform some extra actions.

It might be fixed by providing extra LSP configuration with Tarantool annotations. It needs a little bit of extra support from the language server and from the EmmyLua extension for the Tarantool extension to be able to use non-workspace specific configs. See EmmyLua/VSCode-EmmyLua#216 and EmmyLuaLs/emmylua-analyzer-rust#355

@georgiy-belyanin
Copy link
Member Author

Related PR in LSP EmmyLuaLs/emmylua-analyzer-rust#356

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant