How do I ignore "code issues" and get rid of the swiggly underlines?

[abdulfatir]

System details (run AWS: About and/or Amazon Q: About)

OS: Linux x64 6.8.0-1035-aws Visual Studio Code extension host: 1.103.1 Amazon Q: 1.93.0 node: 22.17.0

Question

I asked a question about my active file and Q started a "code review". How can I get ignore all these issues in the file and get rid of swiggly underlines? I want to go back to a state where the code review never happened. If I click Ignore on individual warnings, it adds # amazonq-ignore-next-line before the line and I do not want to pollute my code with these comments. Ignore All doesn't do what I expected it to do (ignore all issues in the file). Please see the screenshot below:

Related: the issues found by Q are complete nonsense. It complains about an "incomplete function" at an import statement.

[BlakeLazarine]

Hello, thank you for this information. While we do not have a built-in way to accomplish exactly what you want, there are 2 options for you

1. ignore all: permanently ignore all findings with a given name
2. Highlight your whole file, cut the entire code (this will clear the issues from that file in the CodeIssues panel) and then immediately paste the code back.

Thank you for your feedback on the quality of findings, we are actively pursuing a line of work to improve this

[BlakeLazarine]

If you are willing, it would be helpful if you could provide us with the file which generating these findings. It would help us identify false-positives and reproduce situations like this to ensure they do not happen going forward

[brlin-tw]

For the record:

I click Ignore on individual warnings, it adds # amazonq-ignore-next-line before the line

This method does not work at my end(1.99.0) as well:

The extension probably shouldn't provide such a function if it does not work/implemented in the first place.

[pankaj-ispot]

I have the same issue. Highlighting the whole file without any option to disable this feature is very annoying. And the crazy part is, I didn't even ask for it to scan my code and find these issues. On top of that, it lists "implementation follows correct pattern" as a Critical issue.