`rust-analyzer.check.overrideCommand` doc gives a `String` as an example, while `Vec<String>` is expected

[Logarithmus]

https://rust-analyzer.github.io/book/configuration.html#check.overrideCommand claims I can provide a string:

But this didn't work as expected, so I had to check source code and my suspicion was correct, it expects a Vec:

https://github.com/rust-lang/rust-analyzer/blob/8611b714597c89b092f3d4874f14acd3f72f44fd/crates/rust-analyzer/src/config.rs#L844C9-L844C99

[iorizu]

There are two other config options besides check.overrideCommand which only accept Vec<String>: buildScripts.overrideCommand (src) and rustfmt.overrideCommand (src). They should also be updated at the same time.

Would it be preferable to somehow change the types of the three override options to accept strings? Or should the documentation just be updated to reflect the actual types allowed?

[ChayimFriedman2]

We definitely should change the documentation first. After that we can discuss what is the desired shape.