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
HookyQR opened this issue
May 11, 2016
· 1 comment
Assignees
Labels
apibugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseimportantIssue identified as high-priorityverifiedVerification succeeded
Previously (v1.0 and lower) this would replace the file content with "new" as the edit call would validate the range by reducing the infinite end to the end of the file. From version 1.1 (including insider) the infinite end is set to zero instead.
document.validateRange still performs as expected.
I have changed my extension to call validateRange before any edits, but I believe the way the edits worked previously is more logical.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
apibugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseimportantIssue identified as high-priorityverifiedVerification succeeded
Affected
beautify
for VS Code. HookyQR/VSCodeBeautify#14Steps to Reproduce:
Create extension and, with a file open with content:
Previously (v1.0 and lower) this would replace the file content with "new" as the edit call would validate the range by reducing the infinite end to the end of the file. From version 1.1 (including insider) the infinite end is set to zero instead.
document.validateRange
still performs as expected.I have changed my extension to call
validateRange
before any edits, but I believe the way the edits worked previously is more logical.The text was updated successfully, but these errors were encountered: