Figure out long term role of ValueHint
#5764
Labels
A-completion
Area: completion generator
M-breaking-change
Meta: Implementing or merging this will introduce a breaking change.
S-waiting-on-design
Status: Waiting on user-facing design to be resolved before implementing
Milestone
ValueHint
works well for ahead-of-time generated completions as it tells the generator what shell behavior to opt-in to.However, its not really needed with Rust-native completions and actually puts more of a support burden on it.
On top of that, the documentation default is less relevant now that we have typed values. We changed it for Rust-native completions in #5763 as that is still unstable.
The text was updated successfully, but these errors were encountered: