feat(fmt): add support for configuration file

[bartlomieju]

Example config with all supported options:

{
    "fmt": {
        "files": {
            "include": ["src/"],
            "exclude": ["src/testdata/"]
        },
        "options": {
            "useTabs": true,
            "lineWidth": 80,
            "indentWidth": 4,
            "singleQuote": true,
            "textWrap": "preserve"
        }
    }
}

Closes #11857

[dsherret]

The reason this is called text_wrap in dprint-plugin-markdown is because it controls how the Text node wraps. Since this is a top level config and not markdown specific, I think we should call this prose_wrap to align with prettier.

[bartlomieju]

I'm fine with changing name, but I'm unsure about that it's not Markdown specific - I haven't found a setting in dprint-plugin-typescript that would be relevant for this setting. Can you elaborate?

[bartlomieju]

This PR is still missing tests and I will add them tomorrow. @kitsonk can you please review the changes to LSP?

[bartlomieju]

I have trouble with this test, I'm getting following error:

running 1 test
test integration::lsp::lsp_format_with_config ... FAILED

failures:

---- integration::lsp::lsp_format_with_config stdout ----
Some(
    LspResponseError {
        code: -32602,
        message: "missing field `tabSize`",
        data: None,
    },
)
thread 'integration::lsp::lsp_format_with_config' panicked at 'assertion failed: maybe_err.is_none()', cli/tests/integration/lsp_tests.rs:3221:3
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Should I just pass fake data here and count on the fact that config file should take precedence over these options?

CC @kitsonk

[dsherret]

I think that's fine to provide some fake data. The editor will have a "tab size" for a file that might not be synced with the formatting settings.

[dsherret]

LGTM