chore(linter): set 'jsdoc/sort-tags' rule to 'error' #1173
Merged
Conversation
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
xDivisionByZerox
added
c: chore
Codecov Report
@@ Coverage Diff @@
## main #1173 +/- ##
=======================================
Coverage ? 99.64%
=======================================
Files ? 2146
Lines ? 230467
Branches ? 980
=======================================
Hits ? 229657
Misses ? 789
Partials ? 21 |
ejcheng
approved these changes
Jul 20, 2022
ST-DDT
approved these changes
Jul 21, 2022
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.
Since we have no warnings for the
jsdoc/sort-tagseslint rule anymore I promoted its mode from'warning'to'error'as stated in the comment above.