-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[flow] Setup types for extra data for detailedly rendered diagonistics
Summary: In this diff, we setup LSP types for the extra information needed to render detailed errors in vscode. We attach the information in the `data` field of [diagnostic](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#diagnostic), which is guaranteed to not be inspected by standard LSP client, but is something our vscode extension can inspect and do something meaningful. The rendering protocol will introduce a tight coupling between our language server and client, so I also introduced some version scheme. For now, as I am prototyping, I will start with a simple schema that just dumps the CLI error in plaintext form. Therefore, the schema for our data field is: ``` type Data = | null | void | { version: 0, rendered: string } // | ... to be extended in the future ``` We can continue iterating on the v0 design, since it's still unreleased. Changelog: [internal] Reviewed By: panagosg7 Differential Revision: D57169091 fbshipit-source-id: b4dd8ba1031f1384c8aa9e3a44e303b8f53068e4
- Loading branch information
1 parent
b9770f9
commit 8894f2d
Showing
8 changed files
with
53 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters