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
thanks for this great extension, its become an unreplaceable tool for me!
I am currently trying to establish a consistent code style at work, mainly by promoting sqlfluff.
Because we deal with a lot of legacy code, dbt, and the final convention is not established yet, we often cannot get a certain file to comply with sqlfluff. For now, that's okay and part of the transition process.
What would really help in those cases is to be able to disable the linting, either by toggeling the whole extension, or just for the currently open file. However, I have not found a convenient way to do this, say via a UI Button (in the status bar), or via the command palette. So far, my workaround has been to either add -- noqa: disable=all or to go the extension settings and disable there.
Am I missing something obvious, or does anyone have a better workaround?
In any case, this might be a useful feature to have. I could start a PR but havent worked on vs code extensions yet, so some starting clues would be needed!
Cheers,
p
The text was updated successfully, but these errors were encountered:
Hi all,
thanks for this great extension, its become an unreplaceable tool for me!
I am currently trying to establish a consistent code style at work, mainly by promoting sqlfluff.
Because we deal with a lot of legacy code, dbt, and the final convention is not established yet, we often cannot get a certain file to comply with sqlfluff. For now, that's okay and part of the transition process.
What would really help in those cases is to be able to disable the linting, either by toggeling the whole extension, or just for the currently open file. However, I have not found a convenient way to do this, say via a UI Button (in the status bar), or via the command palette. So far, my workaround has been to either add
-- noqa: disable=all
or to go the extension settings and disable there.Am I missing something obvious, or does anyone have a better workaround?
In any case, this might be a useful feature to have. I could start a PR but havent worked on vs code extensions yet, so some starting clues would be needed!
Cheers,
p
The text was updated successfully, but these errors were encountered: