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
You will see a file called issue.txt be automatically opened.
3. Observe that the contents of the MemFS Output channel look like this:
writeFile
readFile
--- content:
foo
---
stat
mtime 1748362486778
stat
mtime 1748362486778
stat
mtime 1748362486778
This is logging the FileSystemProvider events called on issue.txt.
4. Type a "b" after "foo" in issue.txt and save the file.
5. Observe that the editor is showing "foob", but that the text of the file returned by readFile() is now "foobar":
writeFile
stat
mtime 1748362634512
stat
mtime 1748362634512
readFile
--- content:
foobar
---
I expect that the content of the editor would match what is returned by readFile(), especially when the file's mtime has changed.
Steps to Reproduce:
You will see a file called
issue.txt
be automatically opened.3. Observe that the contents of the
MemFS
Output channel look like this:This is logging the
FileSystemProvider
events called onissue.txt
.4. Type a "b" after "foo" in
issue.txt
and save the file.5. Observe that the editor is showing "foob", but that the text of the file returned by
readFile()
is now "foobar":I expect that the content of the editor would match what is returned by
readFile()
, especially when the file'smtime
has changed.vscode-memfs-0.0.4.vsix.zip
The text was updated successfully, but these errors were encountered: