We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
onDidSaveTextDocument
fdir
Rather than using VS Code's onDidSaveTextDocument event, we will instead implement their file watcher
We will move away fdir and use VS Code's fs manager
onDidChange
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issues
onDidSaveTextDocument
event isn't enough to identify external changes (like those from the dev tools).fdir
is a fantastic tool, but there have been a few issues with shadow files and network drives/filesProposal
Rather than using VS Code's
onDidSaveTextDocument
event, we will instead implement their file watcherWe will move away
fdir
and use VS Code's fs managerTODO
fdir
onDidChange
eventShould resolve/close
The text was updated successfully, but these errors were encountered: