How does one ignore folders\files for "Problems"?

sitefinitysteve

1) vendor/composer/ClassLoader is in my problems list... I'd like it to not be lol :)
2) How do I "refresh" what's in there? I had a test that was PEST, moved it over to PhpUnit and the old warnings for it() not being understood were all still there. Weirdly doubleclicking the lines showed me the old file, but opening the file from the explorer showed the NEW file.

I keep slamming up against this, the UI is telling me about all the problems files have, agent investigates says it's not an issue... I click the problem it shows me it's still there, restart VSCode, and the agent was right, I guess I was looking at some cached issue. I'm on the trial and it's not a great experience, am I just missing something?

Thoughts?

Thanks,
Steve

JakubMisek

sitefinitysteve, thank you for reportnig this.

This sounds like a bug which we would be thrilled to fix.

1) The next update will recognize the apcu functions in vendor/composer/ClassLoader; anyways, there are several ways of suppressing problems: https://docs.devsense.com/vscode/problems/suppressing-diagnostics/#phpproblemsexclude

2) This is definitely a bug, because problems are refreshed automatically whenever the file is changed. Do you have a screenshot or more details about the "ghost problems"? Is the project on docker/WSL/remote server?