diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2020-07-21 10:41:54 +0100 |
|---|---|---|
| committer | GitHub <[email protected]> | 2020-07-21 10:41:54 +0100 |
| commit | 818aeb8a242bba5d8947ce2960e1af27d998f4fc (patch) | |
| tree | f61bb82640fd05d1e62cb614ed51cb52eb471ff8 /Cargo.lock | |
| parent | 2ad5bf8d17389e6711be65200ef918762eba9fdc (diff) | |
| parent | a32dd9c478fec0c21fa7416c267bdf1d2416b355 (diff) | |
Merge #5467
5467: Allow null or empty values for configuration r=matklad a=kjeremy
Allow the client to respond to `workspace/configuration` with `null` values. This is allowed per the spec if the client doesn't know about the configuration we've requested.
This also protects against `null` or `{}` during initialize. I'm not sure if we want to interpret `{}` as "don't change anything" but I think that's a reasonable approach to take.
This should help with LSP clients working out of the box.
Fixes #5464
Co-authored-by: kjeremy <[email protected]>
Diffstat (limited to 'Cargo.lock')
0 files changed, 0 insertions, 0 deletions