The KCL LSP resolves symlinks when it shouldn't #1981
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Use linux (I haven't tested on windows) and either IntelliJ or VSCode (not tested with neovim).
Create a kcl file at path /tmp/project/main.k
Create a symbolic link pointing to the "project" directory like so
/tmp/link -> /tmp/project
Open the project in either IntelliJ or VSCode via /tmp/link
2. What did you expect to see? (Required)
Diagnostics and autocomplete
3. What did you see instead (Required)
Nothing, because when looking at the traces from the KCL LSP, it was returning information for /tmp/project/main.k, and so the editor (both intellij and VSCode) were silently ignoring it, since the current opened file is /tmp/link/main.k
4. What is your KCL components version? (Required)
kcl language-server:
Version: 0.11.2-c020ab3eb4b9179219d6837a57f5d323
Platform: x86_64-unknown-linux-gnu
GitCommit: 48c6244