If the current behavior is a bug, please provide the minimal steps to reproduce on the extension
The issue can easily be reproduced by creating a new VSCode project with a single JSON file which can be empty or even very simple.
What is the expected behavior?
If the reported problem is a valid warning from a validation problem, there should be information available on how to resolve the issue. Ideally, the URL in the problem message should lead to documentation describing the issue and how it can be resolved.
Or, at least have a way to configure suppression of irrelevant reported problems.
Please tell us about your environment:
Extension Version: 0.5.18
ALS Distribution: unknown
OS: MacOS Ventura 13.2.1
Link to your project: n/a
Other information (e.g. detailed explanation, stack traces, related issues, workarounds, links for us to have context, eg. StackOverflow, Gitter, etc)
I have asked a similar question on StackOverflow: link
Your issue may already be reported! Please search on Github issues before creating one.
I'm submitting a ...
What is the current behavior?
AML Support is reporting the same problem for all JSON files in project,
The issue can easily be reproduced by creating a new VSCode project with a single JSON file which can be empty or even very simple.
If the reported problem is a valid warning from a validation problem, there should be information available on how to resolve the issue. Ideally, the URL in the problem message should lead to documentation describing the issue and how it can be resolved.
Or, at least have a way to configure suppression of irrelevant reported problems.
Please tell us about your environment:
Other information (e.g. detailed explanation, stack traces, related issues, workarounds, links for us to have context, eg. StackOverflow, Gitter, etc)
I have asked a similar question on StackOverflow: link