CodeQL is missing an inline mechanism to suppress warnings
This was asked about in https://github.com/github/codeql/issues/9298 and the issue log stated "closed as not planned". The "answer" was to dismiss via the UI. But this alone is really not a sufficient mechanism: * Having to interact with the UI is supremely annoying * Spurious new warnings if the code moves cannot be avoided this way * It is _good_ to be forced to comment these exception inline where they happen * What if you are running codeql locally? Then here is _no_ mechanisim? Please consider supporting this basic, table-stakes feature that many, many linting/scanning tools afford.
Posted by bryevdv on Nov 25, 2022, 5:50 AM
Tags
Related issues
- This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
- I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
- the new VSCode UI, looks cute, i don't like it.
- I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
- The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
- Add PR-style review comments in Git Diff UI that feed into the active agent thread
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
ux (Software)
This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
the new VSCode UI, looks cute, i don't like it.
I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
Add PR-style review comments in Git Diff UI that feed into the active agent thread
Thanks for indulging me so far, by the way, I really appreciate this discussion, it's very stimulating.
Migrate GDScript to the GDExtension mechanism and overhaul the implementation
CodeQL is missing an inline mechanism to suppress warnings
This was asked about in https://github.com/github/codeql/issues/9298 and the issue log stated "closed as not planned". The "answer" was to dismiss via the UI. But this alone is really not a sufficient mechanism: * Having to interact with the UI is supremely annoying * Spurious new warnings if the code moves cannot be avoided this way * It is _good_ to be forced to comment these exception inline where they happen * What if you are running codeql locally? Then here is _no_ mechanisim? Please consider supporting this basic, table-stakes feature that many, many linting/scanning tools afford.
Comments (0)
No comments yet. Start the discussion.