diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2021-05-25 13:15:48 +0100 |
|---|---|---|
| committer | GitHub <[email protected]> | 2021-05-25 13:15:48 +0100 |
| commit | 835cf55887527bd1953cb7004259214f7c215095 (patch) | |
| tree | dadc26f171812663779a80cbe9344e9a004b37e7 /crates/syntax/test_data/parser/fragments/expr/ok | |
| parent | b7414fa14a85f4acd37b5bdfdc2a4ab97a072bd2 (diff) | |
| parent | a90b9a5872c9c916733816e1e0d8c95cb09bfcba (diff) | |
Merge #8767
8767: implement range formatting r=matklad a=euclio
Fixes #7580.
This PR implements the `textDocument/rangeFormatting` request using `rustfmt`'s `--file-lines` option.
Still needs some tests. What I want to know is how I should handle the instability of the `--file-lines` option. It's still unstable in rustfmt, so it's only available on nightly, and needs a special flag to enable. Is there a way for `rust-analyzer` to detect if it's using nightly rustfmt, or for users to opt-in?
Co-authored-by: Andy Russell <[email protected]>
Diffstat (limited to 'crates/syntax/test_data/parser/fragments/expr/ok')
0 files changed, 0 insertions, 0 deletions