meta: Eslint JSDoc plugin #147
Open
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
RedYetiDev
reviewed
Nov 16, 2024
There was a problem hiding this comment.
Is there a reason why the recommended config can't be used?
jsdoc.configs['flat/recommended-error']
There was a problem hiding this comment.
There seem to be stricter rules than the ones we apply, I can even say that I am against some of the rules being applied as recommended
I tried to combine the rules we already apply as much as possible when using/developing features or for a more efficient review process
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.
Description
I thought the Eslint JSDoc rules would make sense for comments that we might miss or were not properly formatted. I've updated the missing or incorrectly indented sections with this PR
Check List