-
Notifications
You must be signed in to change notification settings - Fork 29.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
folder rename does not result in updated path #164562
Labels
Milestone
Comments
mjbvz
added
markdown
Markdown support issues
bug
Issue identified by VS Code Team member as probable bug
labels
Oct 25, 2022
mjbvz
added a commit
to mjbvz/vscode
that referenced
this issue
Oct 26, 2022
mjbvz
added a commit
that referenced
this issue
Oct 26, 2022
vscodenpa
added
unreleased
Patch has not yet been released in VS Code Insiders
insiders-released
Patch has been released in VS Code Insiders
and removed
unreleased
Patch has not yet been released in VS Code Insiders
labels
Oct 26, 2022
formigoni
pushed a commit
to formigoni/vscode
that referenced
this issue
Oct 27, 2022
joyceerhl
added
verification-found
Issue verification failed
and removed
verified
Verification succeeded
labels
Oct 27, 2022
vscodenpa
removed
the
insiders-released
Patch has been released in VS Code Insiders
label
Oct 27, 2022
mjbvz
added a commit
to mjbvz/vscode
that referenced
this issue
Oct 27, 2022
Fixes microsoft#164562 My previous fix was incorrect as it checked if the document existed by still consulting our `_documentCache`. When we are deleting/renaming an opened md document, it should pretty much always exist in our cache The fix is to instead treat `this.documents` and the file system as the source of truth when determining if the doc should be deleted or not
mjbvz
added a commit
that referenced
this issue
Oct 27, 2022
Fixes #164562 My previous fix was incorrect as it checked if the document existed by still consulting our `_documentCache`. When we are deleting/renaming an opened md document, it should pretty much always exist in our cache The fix is to instead treat `this.documents` and the file system as the source of truth when determining if the doc should be deleted or not
vscodenpa
added
unreleased
Patch has not yet been released in VS Code Insiders
insiders-released
Patch has been released in VS Code Insiders
and removed
unreleased
Patch has not yet been released in VS Code Insiders
labels
Oct 27, 2022
andreamah
added
verified
Verification succeeded
and removed
verified
Verification succeeded
labels
Oct 28, 2022
vscodenpa
removed
the
insiders-released
Patch has been released in VS Code Insiders
label
Oct 28, 2022
Ugh this bug :/ I'm marking it as a candidate because I'm pretty sure the root cause (#164942) effects other markdown features too |
mjbvz
added
the
candidate
Issue identified as probable candidate for fixing in the next release
label
Oct 28, 2022
mjbvz
added a commit
to mjbvz/vscode
that referenced
this issue
Oct 29, 2022
This is a cherry pick of two fixes: - microsoft#164945 which fixes microsoft#164932 by picking up a new md language service version - microsoft#164942 which fixes microsoft#164562 by fixing a bug with the md workspace implementation
mjbvz
added a commit
that referenced
this issue
Oct 31, 2022
rzhao271
added
verified
Verification succeeded
and removed
verification-found
Issue verification failed
labels
Dec 29, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Testing #164522
Given this setup:
renaming folder "foo" to "bar" does trigger the prompt but the path "/foo/file_2.md" is not updated (and gets broken).
The text was updated successfully, but these errors were encountered: