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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[api-extractor] Add options to include forgotten exports in API report and doc model files #3552
[api-extractor] Add options to include forgotten exports in API report and doc model files #3552
Changes from 6 commits
42ab8f0
d0393b0
f9a98d4
d4e758d
84de9f3
3b2129d
02ee8a0
d9a0587
54db4bb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change prevents unexported items included in an API report from being assigned the
@public
release tag if none is specified.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After some discussion, I think this logic is not right. The "effective" release tag must always be something other than
ReleaseTag.None
.The simplest approach would be to handle forgotten exports like any other API item:
@public
(because in this case, the developer presumably doesn't care very much about trimming or release tags)Note that when
includeForgottenExports=false
then this validation is not useful, and prior to this PR, API Extractor would not complain about problems with forgotten exports. But withincludeForgottenExports=true
we probably do want such validation.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated this PR to match the behavior you described above. However, I was thinking a bit more about forgotten exports and release tags and sent you a message on Zulip, reproduced below:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, but I think we could implement that extra validation in a separate PR.