We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
src
*.v files that are not in the src folder do not appear to be fully analyzed.
*.v
Here is a screenshot from VS Code:
As you can see, semantic highlighting is working, but not diagnostics. There is no function http.new_resonse in scope.
http.new_resonse
An editor diagnostic similar to what happens in the CLI when the file is invoked.
main.v:22:14: error: unknown function: net.http.new_resonse . Did you mean `net.http.new_response`? 20 | header.add(http.CommonHeader.content_type, 'text/html') 21 | 22 | return http.new_resonse(http.ResponseConfig{ body: 'Hello', header: header }) | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 23 | }
No diagnostic was presented.
mkdir example cd example v init mv src/main.v main.v echo "module main fn main() { printlm('Hi there!') } " > main.v code .
No response
v doctor
V full version: V 0.4.6 100b3b0 OS: macos, macOS, 14.5, 23F79 Processor: 8 cpus, 64bit, little endian, Apple M1 Pro
getwd: /Users/elijah.mooring/Projects/v vexe: /Users/elijah.mooring/Projects/v/v vexe mtime: 2024-06-11 02:11:54
vroot: OK, value: /Users/elijah.mooring/Projects/v VMODULES: OK, value: /Users/elijah.mooring/.vmodules VTMP: OK, value: /tmp/v_503
Git version: git version 2.39.3 (Apple Git-146) Git vroot status: weekly.2024.24-1-gdfdd7521-dirty .git/config present: true
CC version: Apple clang version 15.0.0 (clang-1500.3.9.4) thirdparty/tcc status: thirdparty-macos-arm64 5c1d002f
VSCode
v-analyzer version 0.0.4-beta.1.7e11a6f
v0.0.2
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
*.v
files that are not in thesrc
folder do not appear to be fully analyzed.Here is a screenshot from VS Code:
As you can see, semantic highlighting is working, but not diagnostics. There is no function
http.new_resonse
in scope.Expected Behavior
An editor diagnostic similar to what happens in the CLI when the file is invoked.
Current Behavior
No diagnostic was presented.
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
Environment details (
v doctor
output)V full version: V 0.4.6 100b3b0
OS: macos, macOS, 14.5, 23F79
Processor: 8 cpus, 64bit, little endian, Apple M1 Pro
getwd: /Users/elijah.mooring/Projects/v
vexe: /Users/elijah.mooring/Projects/v/v
vexe mtime: 2024-06-11 02:11:54
vroot: OK, value: /Users/elijah.mooring/Projects/v
VMODULES: OK, value: /Users/elijah.mooring/.vmodules
VTMP: OK, value: /tmp/v_503
Git version: git version 2.39.3 (Apple Git-146)
Git vroot status: weekly.2024.24-1-gdfdd7521-dirty
.git/config present: true
CC version: Apple clang version 15.0.0 (clang-1500.3.9.4)
thirdparty/tcc status: thirdparty-macos-arm64 5c1d002f
Editor name
VSCode
v-analyzer Version
v-analyzer version 0.0.4-beta.1.7e11a6f
VS Code Extension Version
v0.0.2
The text was updated successfully, but these errors were encountered: