LuaLS / LuaLS/lua-language-server
Relative paths for library files break in a multi workspace setup
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 4.4k
- Forks
- 442
- PR merge metrics
- No merged PRs in 30d
Description
Vscode Latest
log.log
Each workspace has it its own .luarc file
If I use a relative path for workspace.library in a multi workspace setup "../../factorio-api/", then the files are not used correctly
However if I use an absolute path for a workspace, that workspace will work correctly
This does not happen if the relative path is in only 1 of the workspaces with the other being empty
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in VS Code with two workspaces, each using its own .luarc and a relative workspace.library path such as "../../factorio-api/". Review the attached log.log while comparing this setup with the working absolute-path and single-workspace cases. Done means relative library paths resolve correctly for every workspace in the multi-workspace setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100