Jsdoc: enable eslint rule valid-jsdoc.preferType #30509
Merged
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
Mugen87
reviewed
Feb 12, 2025
s-rigaud
force-pushed
the
implement-valid-jsdoc-preferType
branch
2 times, most recently
from
d88fa40 to
6a9b721
Compare
Mugen87
approved these changes
Feb 12, 2025
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
In the same spirit as #30466 which tries to update code as close to Jsdoc official typing as possible, I added the eslint rule valid-jsdoc.preferType to enforce eslint to follow the official doc for future development.
I re-run all the linting commands, found nothing to update in the core folder as everything was nicely updated in the previous PR but I updated the files that needed changes in other folders to avoid adding additional linting errors.