Closed jryans closed 2 months ago
I believe this is happening because the extension provides the following document selector to the language server client:
The language server client then uses that to register support for various features (including formatting). The scheme: "file"
portion only matches saved buffers, so that's probably the thing to change here.
The tricky part though is we may have some features that don't work for unsaved buffers (even if formatting can), and changing this global line would mark all language features as supported for unsaved buffers... Some testing is certainly needed before doing that.
Steps to reproduce
Expected
The file should be formatted.
Actual
VS Code claims "There is no formatted for 'racket' files installed."