chore: re-enabled jsdoc/tag-lines rule, ran lint:fix script to fix linting issues#2066
Merged
BeksOmega merged 2 commits intoRaspberryPiFoundation:masterfrom Nov 8, 2023
Conversation
BeksOmega
approved these changes
Nov 8, 2023
Contributor
BeksOmega
left a comment
BeksOmega
left a comment
There was a problem hiding this comment.
This LGTM! Thank you for the fix!
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
3 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.
The basics
The details
Resolves
Fixes #1979
Proposed Changes
Enforced a recommended blank line rule preceding only the first tag (e.g.,
@param) in a jsdoc comment.An Example
Reason for Changes
Code changes are made for better readability of jsdoc comments.
Test Coverage
N/A
Documentation
N/A
Additional Information
Running
npm run lintshows 16 warnings but that's being fixed in #2065.