config: Add Configuration for Progress Reporting Verbosity

[davidbarsky]

At work, some of the indexing would take up the entire status bar because of buck-out has some pretty long paths. This is an option to make it less chatty/loud.

[lnicola]

This feels a bit confusing (I'd expect [] to mean that nothing is reported, with null being the default).

But I also don't see what makes it behave like the docs say (that is, report the directories when this is set to []).

[davidbarsky]

Ah crud, I think I got the options here flipped. Lemme fix that.

[Veykril]

This feels like a very odd config to me I have to say 😅 Does VSCode hide elements in the status bar if the messages are too long? (As in does it overflow into other elements?)

[davidbarsky]

This feels like a very odd config to me I have to say 😅 Does VSCode hide elements in the status bar if the messages are too long?

It is a weird config, I agree.

As in does it overflow into other elements?

Yeah, it overflows and flashes in a weird, somewhat unpleasant way. This config working around that.

[Veykril]

Ugh, I wonder if we can override the handling in the client code and just filter too long ones / replace the middle or something with ... to get below a character limit.

Edit: Looks like there is a handleWorkDoneProgress hook

[bors]

☔ The latest upstream changes (presumably #16662) made this pull request unmergeable. Please resolve the merge conflicts.

[Veykril]

So I am still not on board with the idea of a config for this honestly speaking, not sure what to do here.

Though now I'm wondering, are you saying absolute paths in there? Or are your projects just that deep that the paths relative to the project root are very long? If they are absolute than that sounds like we have a mismatch between paths and the project root path for you here.

[davidbarsky]

So I am still not on board with the idea of a config for this honestly speaking, not sure what to do here.

Though now I'm wondering, are you saying absolute paths in there? Or are your projects just that deep that the paths relative to the project root are very long? If they are absolute than that sounds like we have a mismatch between paths and the project root path for you here.

I completely forgot about this PR!

Or are your projects just that deep that the paths relative to the project root are very long?

It's this one. The paths easily extend beyond 100 characters and it leads to a lot of flashing in the status bar. It's generally not an issue with something like ~/.cargo/bin/registry, but proc macros under Buck have some pretty deeply nested paths.

[Veykril]

I wonder if we should just do the easy thing and truncate the paths to some arbitrary length (counting from the end of the path)?