Prevent "Specified path does not exist" error for empty untitled files #149
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I use the vscode-sqlfluff extension with Azure Data Studio. I recently moved to a new computer and after getting ADS set back up, I noticed that the extension was throwing an error saying "User Error: Specified path does not exist. Check it/they exist(s): ." whenver I open a new file (via File > New Query or right clicking on a database and clicking New Query).
The error only happens when the file first opens and is empty. As soon as the file has text/sql in it, the extension works and lints the file as expected. Nothing changed with my local extension config when I moved my files to the new computer (I did download the latest version of SqlFluff so it's possible I have newer version of that, but I can't remember what version I had installed on my old PC), so I'm not sure what would cause this error to start occuring all of the sudden.
Since it's not really necessary to lint an empty file, I thought an easy fix would be to skip linting when you're in an untitled file that's empty. I tested locally with this change and everything worked as expected. I also had a coworker who was experiencing the error do some testing and they reported no longer seeing the error with this change.