fix(complete): Change ValueHint::Unknown to Other, from AnyPath #5763
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`AnyPath` is the documented behavior *but* thats to help when there isn't much other information. With us choosing a `ValueHint` based on the value parser, we are less likely to get benefit from `AnyPath`. Instead, this will greatly improve cases like Cargo where we offer path completions on many arguments where it doesn't make sense.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AnyPathis the documented behavior but thats to help when there isn't much other information. With us choosing aValueHintbased on the value parser, we are less likely to get benefit fromAnyPath.Instead, this will greatly improve cases like Cargo where we offer path completions on many arguments where it doesn't make sense.