-
Notifications
You must be signed in to change notification settings - Fork 10
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
Allow stopping of extension processing after comment line #55
Comments
It is possible. The concern is that the user may be confused as to whether to disable the entire subsequent file or only the following statement. Perhaps an option to disable the following statement should be provided at the same time
Also, I believe this issue is connected to #12 where we wanted to control by comments. I am waiting for a parser to interpret comments, but perhaps I should include own processing. In any case, I don't have time right now to get into this issue right away. |
We have released v2.10.0. In this release, it is possible to perform validation on each statement divided by comments and set the disable flag for each statement. Please see this sample. If this feature works for your purposes, please close this PR. |
Please also refer to the following https://github.com/UniqueVision/plpgsql-lsp#multiple-statements |
Is your enhancement related to a problem? Please describe.
Currently, /* plpgsql-language-server:disable */ is supported to disable extension processing for entire file.
Would it be possible to stop any extension processing beyond the comment as opposed to whole file?
My use case is for a data processing test script like
It would be great to allow the extension to give me feedback as normal on my tables,function definitions, but not execute the function at the bottom.
So if the extension supported:
The text was updated successfully, but these errors were encountered: