feat(api-extractor): Allow users to customize which TSDoc tags are reported in generated API reports #5079
+149
−21
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
Josmithr
commented
Jan 14, 2025
| * | ||
| * Note that an item's release tag will always reported; this behavior cannot be overridden. | ||
| * | ||
| * @defaultValue `@sealed`, `@virtual`, `@override`, `@eventProperty`, `deprecated` |
There was a problem hiding this comment.
TODO: Add examples
Josmithr
force-pushed
the
api-extractor/custom-tags
branch
from
e81364b to
6dab01c
Compare
Josmithr
commented
Feb 4, 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.
Allow users to configure which TSDoc tags appear in API reports.
Issue #4988