You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While calculating the replacement range, given the current token (which is currently coerced into one line), it assumes that the whole thing is in one line, which causes the range to have a negative column. Unfortunately, the output of completions are also split on that newline, so we cannot actually use the output. Again, this would be a non-issue with #209, but I have not figured it out yet. Regardless, to solve it without a parser, we can consider only the last line of the argument and modify that only, skipping the other lines in the completions.
The text was updated successfully, but these errors were encountered:
While calculating the replacement range, given the current token (which is currently coerced into one line), it assumes that the whole thing is in one line, which causes the range to have a negative column. Unfortunately, the output of completions are also split on that newline, so we cannot actually use the output. Again, this would be a non-issue with #209, but I have not figured it out yet. Regardless, to solve it without a parser, we can consider only the last line of the argument and modify that only, skipping the other lines in the completions.
The text was updated successfully, but these errors were encountered: