You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a <> in a .yarn file, calling a custom command with the incorrect number or types on command arguments are not indicated as errors on in the Issues tab.
Functions behave correctly.
Please provide the steps to reproduce, and if possible a minimal demo of the problem:
Implement a basic custom command that takes one int as an argument, e.g.,
What is the current behavior?
When using a <> in a .yarn file, calling a custom command with the incorrect number or types on command arguments are not indicated as errors on in the Issues tab.
Functions behave correctly.
Please provide the steps to reproduce, and if possible a minimal demo of the problem:
e.g.,
What is the expected behavior?
The above examples should show an issue in the "Issues" tab in vscode.
Number "4" might be trickier, since it's probably ok to pass numbers as unquoted strings for a command that accepts strings.
Please tell us about your environment:
Other information
The text was updated successfully, but these errors were encountered: