-
Notifications
You must be signed in to change notification settings - Fork 16
Issues: vlang/v-analyzer
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Debug Adaptor Protocol Support.
enhancement
New feature or request
#137
opened Oct 31, 2024 by
KeitoTobi1
v-analyzer up
and v-analyzer check-updates
fail with: "Invalid header key: 'Cache-Control'"
bug
#136
opened Oct 28, 2024 by
skull-squadron
V-analyzer slowly leaks memory over time
bug
Something isn't working
Confirmed
#131
opened Oct 10, 2024 by
4hnme
[Docs] Add a list of supported/unsupported features
bug
Something isn't working
documentation
Improvements or additions to documentation
enhancement
New feature or request
#129
opened Sep 22, 2024 by
lcheylus
Large const map causes extreme v-analyzer performance degradation
bug
Something isn't working
#115
opened Aug 1, 2024 by
einar-hjortdal
The LSP configuration on Neovim is wrong.
bug
Something isn't working
#114
opened Jul 26, 2024 by
JulienLecoq
v-analyzer segmentation fault on large files/projects
bug
Something isn't working
#110
opened Jun 19, 2024 by
JalonSolov
Files outside the Something isn't working
src
folder are not fully analyzed
bug
#107
opened Jun 11, 2024 by
Vehmloewff
Rename, hover, go to definition and completion are not working properly for this sample code
bug
Something isn't working
#105
opened May 22, 2024 by
resolritter
Publish diagnostics even if the file is not saved to disk
enhancement
New feature or request
help wanted
Extra attention is needed
#104
opened May 21, 2024 by
resolritter
Server crashed when method called on Something isn't working
it
bug
#103
opened Apr 29, 2024 by
benash
errors in script mode Something isn't working
bad top level statement […]
bug
#98
opened Apr 15, 2024 by
ttytm
the vscode extension should be more lax in finding the v-analyzer executable
bug
Something isn't working
VS Code Extension
ProTip!
Follow long discussions with comments:>50.