Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Provide an option to suppress errors generated by JsDoc #11639

Closed
zhengbli opened this issue Oct 14, 2016 · 1 comment
Closed

Provide an option to suppress errors generated by JsDoc #11639

zhengbli opened this issue Oct 14, 2016 · 1 comment
Labels
Domain: JSDoc Relates to JSDoc parsing and type generation

Comments

@zhengbli
Copy link
Contributor

Binding errors like "Duplicate identifiers" can be generated by JsDoc comments in JavaScript file, however as they are not technically part of the code, it would be too strict to block compiling due to these errors, especially when the code is from somewhere else. We should at least provide a compiler option to suppress diagnostics in JsDoc comments.
@zhengbli zhengbli changed the title Provide options to suppress binding errors generated by JsDoc Provide an option to suppress binding errors generated by JsDoc Oct 14, 2016
@zhengbli zhengbli changed the title Provide an option to suppress binding errors generated by JsDoc Provide an option to suppress errors generated by JsDoc Oct 14, 2016
@mhegazy
Copy link
Contributor

mhegazy commented Oct 17, 2016

We can suppress these errors by default. we can enable them later on as part of #6802

@mhegazy mhegazy closed this as completed Dec 15, 2016
@mhegazy mhegazy added the Domain: JSDoc Relates to JSDoc parsing and type generation label Dec 15, 2016
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Domain: JSDoc Relates to JSDoc parsing and type generation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zhengbli @mhegazy