The usage scenario is as follows: I imported a third-party package outside the workspace through the "source-path" in “asconfig. json”, but due to the third-party code writing is not standard, VSCode shows that there are 1k+ warnings.
So I need a feature that hide all warnings for files in this path, while retaining the "errors" so I can find problems in the source code.
I have already written in settings.json: “as3mxml.problems.showFileOutsideSourcePath”: false, but it doesn’t help. So I am asking the author if there is a feature that can solve this problem, or if it is possible to add this feature to the development plan.
Also: I know that VSCode has its own problem filter, but it doesn’t work well. It counts the filtered issues as part of the total number of badges; the filtering strategy cannot be recorded in a file.
The usage scenario is as follows: I imported a third-party package outside the workspace through the "source-path" in “asconfig. json”, but due to the third-party code writing is not standard, VSCode shows that there are 1k+ warnings. So I need a feature that hide all warnings for files in this path, while retaining the "errors" so I can find problems in the source code.
I have already written in settings.json: “as3mxml.problems.showFileOutsideSourcePath”: false, but it doesn’t help. So I am asking the author if there is a feature that can solve this problem, or if it is possible to add this feature to the development plan.
Also: I know that VSCode has its own problem filter, but it doesn’t work well. It counts the filtered issues as part of the total number of badges; the filtering strategy cannot be recorded in a file.
Thank you!!!