Warning message when jsDocParsingMode is not hacked.
#879
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.
As TypeScript starts skipping parsing
JSDocComments since TypeScript v5.3 update but it is possible to revive theJSDocComments' parsing, by hacking thejsDocParsingModevalue oftsc.js, I've decided to print a warning message fromtypiawhen thejsDocParsingModevalue is not hacked.Therefore, it is possible to running the
typiaas before even when thejsDocParsingModehas not benn hacked, and user can ignore the warning message if he (or she) does not use any comment tags and not generating any JSON schema with description comments in the application.