-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[flow][lsp] No-op when given null json as configuration change update
Summary: Similar to the logic [here](https://github.com/facebook/flow/blob/cf97273874d14dec2f0a5b6cb144793a2dcabbd6/src/lsp/flowLsp.ml#L1984-L1985), we need to special case null, otherwise we might just randomly overriding previously configured client back to default, when we decide to pull new configuration from client. I think it is one of the reason why the client override of the detailed error feature doesn't work quite reliably, which is not that surprising, given that these client overrides are never exercised a lot by end users. Changelog: [internal] Reviewed By: panagosg7 Differential Revision: D58071178 fbshipit-source-id: 8abc663b1a0dbf511a5ca63c6af9e0eb846b1011
- Loading branch information
1 parent
d22d9ca
commit 950c5f7
Showing
1 changed file
with
43 additions
and
37 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