Language server as per LSP documentation can support textDocument/formatting method, which is called in any LS clients (mainly in editors) whenever whole file formatting is needed.
At the moment, this plugin has formatting implemented as a VSCode-only feature and not a part of LSP specification, which results in failure to format Tact code when the language server of this plugin is used independently (i.e. here) — a message such as this is shown: "textDocument/formatting not supported for tact".
The solution would be to register formatting capabilities and handle the textDocument/formatting request.
Additionally, there are two similar methods specified in LSP, which may also be handled to further improve UX:
Language server as per LSP documentation can support textDocument/formatting method, which is called in any LS clients (mainly in editors) whenever whole file formatting is needed.
At the moment, this plugin has formatting implemented as a VSCode-only feature and not a part of LSP specification, which results in failure to format Tact code when the language server of this plugin is used independently (i.e. here) — a message such as this is shown:
"textDocument/formatting not supported for tact"
.The solution would be to register formatting capabilities and handle the
textDocument/formatting
request.Additionally, there are two similar methods specified in LSP, which may also be handled to further improve UX: