More strict linting of jsdocs - #7236
Merged
Merged
Conversation
Use TODO over any when type is possible
Contributor
|
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
montogeek
approved these changes
May 8, 2018
ooflorent
approved these changes
May 8, 2018
|
Hey Webpack contributors, don't know if you've seen this before -- but it was news to me that TypeScript is actually using a "fork" of JSDoc called AEDoc. Mostly the same, but a few differences. https://github.com/Microsoft/web-build-tools/wiki/API-Extractor-%7E-AEDoc-tags |
Member
Author
|
@RemyRylan Thanks for this info. Does this also apply here? We are not writing Typescript files but Javascript files. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
lint
Did you add tests for your changes?
n/a
If relevant, link to documentation update:
n/a
Summary
More strict linting of jsdocs
Use TODO over any when type is possible
Does this PR introduce a breaking change?
no
Other information