-
Notifications
You must be signed in to change notification settings - Fork 77
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
Incorrect type flags used to mark parameters and functions #408
Comments
Hey there :) |
For packages (say However, when I invoke this function, typst-lsp prompts that it is a constant again. The image below shows how LuaLs works. It displays the comment of a function, and the information about parameters of this function: it takes only one parameter, |
I see thanks, it's clearer now ;) |
This is probably a good first issue (I haven't investigated but it doesn't seem too complex). What do you think @Myriad-Dreamin ? |
typst-lsp just uses typst-ide for autocompletion. So imo, the inperfect is more probably caused by typst-ide, and less by typst-lsp. @astrale-sharp Is it time to check it by our awesome ide testing framework, :)? Lines 426 to 429 in 0d5b933
|
Agreed, this is almost certainly a Typst bug. From a quick look at the relevant code, the |
Unfortunately I just added functionality for testing the actual string being autocompleted, not it's kind which is globally a bit more weird to check if there are many possible completions 😅 |
Then I propose we should close this and open a typst issue, any objection @Complex2-Liu ? |
We may open a typst issue and keep this open. And this can be closed once the upstream bug get fixed |
Feature Request
Motivated by package tidy. See also LuaLs for someone familiar with Neovim.
The text was updated successfully, but these errors were encountered: