Multiple examples: Fix comments to satisfy JSDoc lint warnings #2032
Conversation
This file contains 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
Autofixed with `npm run lint:es -- --fix`
mcking65
changed the title
|
Thank you @nschonni. Looks like we have a rule that doesn't prefer blank lines in comments between parm descriptions. Do we care about this? Is this something we want to enforce? If so, should we look at the warnings from the linter during code review? If not, should we disable the warning? Does this deserve time on the meeting agenda? |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Autofixed with
npm run lint:es -- --fix