Signature help - handle pipes #624
Merged
Conversation
This file contains hidden or 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
… in preparation for handling expressions with pipe
zth
commented
Nov 7, 2022
| if !foundFunctionApplicationExpr = None then | ||
| foundFunctionApplicationExpr := Some r | ||
| in | ||
| let searchForArgWithCursor ~isPipeExpr ~args ~exp = |
There was a problem hiding this comment.
This whole function body is just moved in here from below, with very minor changes.
cristianoc
approved these changes
Nov 8, 2022
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.
Previously, the signature help wouldn't understand pipes, meaning signature help for piped expressions would always be off by one when having unlabelled arguments. This diff fixes the signature help to account for pipes when present.
Closes #618