We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I toggled each of my 88 extensions to identify this one as the culprit for the strange issue of Go linting errors showing up in my typescript code:
exported identifier <T> should have comment or be unexported
For example:
Install extension. Write typescript where you export an uncomment const function
const
Node: 18.12.1 - /usr/local/bin/node
npm
The text was updated successfully, but these errors were encountered:
Not related solely to this extension. Closing.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
I toggled each of my 88 extensions to identify this one as the culprit for the strange issue of Go linting errors showing up in my typescript code:
For example:
Reproduction
Install extension. Write typescript where you export an uncomment
const
functionSystem Info
Used Package Manager
npm
Validations
The text was updated successfully, but these errors were encountered: