LuaLS / LuaLS/lua-language-server

Code formatting doesn't work when plugin is used.

Open
#2,165 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
4.4k
Forks
442
PR merge metrics
No merged PRs in 30d

Description

### How are you using the lua-language-server?

Visual Studio Code Extension (sumneko.lua)

### Which OS are you using?

Windows

### What is the issue affecting?

Formatting, Plugins

### Expected Behaviour

Code formatting should work when plugin is used.

### Actual Behaviour

Code formatting doesn't work when plugin is used.

### Reproduction steps

1. Create plugin and set the appropriate settings as described here https://github.com/LuaLS/lua-language-server/wiki/Plugins
2. Use it (create some file and use custom syntax)
3. Make some ugly indentation.
4. Alt+shift+f (Format document)
5. The code has not been formatted.
![2023-06-15_12h14_03](https://github.com/LuaLS/lua-language-server/assets/36280384/446e1e24-cebf-4f1d-a762-88c64ef61d43)

### Additional Notes

As you can see the error occurs in VSC but I use LSP mainly as a server for my own client in React and the error also occurs there.

### Log File

[myLog.txt](https://github.com/LuaLS/lua-language-server/files/11756298/myLog.txt)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure using the listed Visual Studio Code steps and a plugin with custom syntax. Compare the behavior with the supplied myLog.txt, including the React LSP client report. Done means formatting applies the expected indentation to files using plugin-defined syntax.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.