LuaLS / LuaLS/lua-language-server
Support for module-style includes?
Ninguém assumiu esta issue ainda.
- Linguagem predominante
- Lua
- Estrelas
- 4.4k
- Forks
- 442
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
How are you using the lua-language-server?
Other
Which OS are you using?
Windows
What is the issue affecting?
Diagnostics/Syntax Checking
Expected Behaviour
Lua files from my project are found automatically without adding a workspace library path.
Actual Behaviour
Incorrect diagnostics due to LSP seemingly being unable to find the lua files in the path. Also go to definition and such don't work.
Reproduction steps
.
Additional Notes
I have a lot of files in my project which I import like so:
import 'game.physics'
import 'game.ball.request'
import 'game.world'
Note that we use import instead of require. It doesn't do anything special regarding the paths, and I have the following setting:
"Lua.runtime.special": {
"import" : "require"
}
These paths are relative to the workspace, plus some folders. The actual paths are like so:
<workspace>/src/script-game/game/physics.lua
<workspace>/src/script-game/game/ball/request.lua
<workspace>/src/script-game/game/world.lua
From reading the documentation, it seems like the default Lua.runtime.path should pick these files up no problem, but I get diagnostics like "Undefined global "physics"", and I can't go to definition or get completions for those files (details omitted, sorry):
If I then add a config for Lua.workspace.library, I can make it work:
"Lua.workspace.library": [
"<workspace>\\src\\script-game"
],
But this feels wrong. These are my files and they're part of my project. I shouldn't need to add them as a library path, should I? Additionally, I could only get it to work as an absolute path, so I need to update this whenever I switch projects. I tried "src/script-game" and "src\script-game" and both reverted back to the broken behaviour.
Am I missing something? Do I need to set something custom in Lua.runtime.path?
Log File
Unfortunately I can't provide this as most of it is under NDA.
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Direção de pesquisa
Comece comparando as configurações Lua.runtime.path, Lua.workspace.library e Lua.runtime.special descritas na issue, especialmente com import mapeado para require. Reproduza as importações relativas ao projeto em src/script-game e verifique se os diagnósticos, ir para definição e complementações funcionam sem um caminho absoluto de biblioteca.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- lua
- Domínio
- tooling
- Tipo de issue
- Funcionalidade
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 35/100