SmallLanguageServerfixes(togetVSCodeextensionworking)

• This PR contains a set of minimal changes to the Language Server code


• They are critical for some users who are running into issues when trying to use the VSCode extension (see #1261)


• I am keeping them as small and self-contained as possible so we can release a patch ASAP

Suppress most error responses from the Language Server

• By patching the
  

  1	lsp.Connection

  object (the top-most entry point), we're catching all errors that would otherwise result in VSCode showing a warning (or worse, an information message that doesn't go away)



• This is brute force, but it is still correct (DX-wise). We want the IDE to support all kinds of malformed projects without failing (just suppressing functionality). We're still logging the errors to the Redwood Language Server output channel.


• Eventually, some of the errors that will get logged should be addressed more granularly at the structure/model level

Improve initialization order of LSP components

• After looking at some usage logs I found sporadic "unhandled method" exceptions (thrown by the LSP client on the VSCode extension side) that were, in some cases, resulting in an empty outline, or in the extension host shutting down the extension altogether. It is hard to understand the race conditions involved, but initializing them as early as possible is a simple, albeit blunt, solution.


• This is a really small fix that changes the initialization sequence of parts of the language server


• It makes sure that several request handlers (commands, outline, etc) are installed as early as possible in the initialization process

Tolerate certain missing files and folders

• Do not throw if schema.prisma does not exist or cannot be parsed


• Do not throw "pages" folder does not exist (or processPagesDir fails)


• More info in this issue comment

该提问来源于开源项目：redwoodjs/redwood