aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/test_data/parser/fragments/item/ok
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2020-07-21 10:41:54 +0100
committerGitHub <[email protected]>2020-07-21 10:41:54 +0100
commit818aeb8a242bba5d8947ce2960e1af27d998f4fc (patch)
treef61bb82640fd05d1e62cb614ed51cb52eb471ff8 /crates/ra_syntax/test_data/parser/fragments/item/ok
parent2ad5bf8d17389e6711be65200ef918762eba9fdc (diff)
parenta32dd9c478fec0c21fa7416c267bdf1d2416b355 (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 'crates/ra_syntax/test_data/parser/fragments/item/ok')
0 files changed, 0 insertions, 0 deletions