Inlay Hint Support #2133
Draft
Inlay Hint Support #2133
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
|
@MartinGC94 @andyleejordan @SeeminglyScience need to find where PSES gets this info from: EDIT: Found it, |
andyleejordan
force-pushed
the
main
branch
2 times, most recently
from
caa9e27 to
677f42c
Compare
andyleejordan
force-pushed
the
main
branch
2 times, most recently
from
80b2351 to
9ce8911
Compare
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.
PR Summary
This PR implements Inlay Hints to resolve the type in PowerShell when it can be determined by the PowerShell Type Inference completer. This is considered best effort and not exhaustive.
NOTE: This PR uses some modern C# syntax features that do not match the prevailing style. Worth exploring if these are OK to adopt: