LuaLS / LuaLS/lua-language-server
Support for module-style includes?
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Lua
- Estrellas
- 4.4k
- Forks
- 442
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
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.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comience comparando las opciones Lua.runtime.path, Lua.workspace.library y Lua.runtime.special descritas en el issue, especialmente con import asignado a require. Reproduzca las importaciones relativas al proyecto bajo src/script-game y verifique que los diagnósticos, ir a la definición y las completaciones funcionen sin una ruta absoluta de biblioteca.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- lua
- Área
- tooling
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100