Repository navigation
build: ship XML docs in the package - #3
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KyLMW81KxVvWKTFU1iDYFo
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Turns on
GenerateDocumentationFileinDirectory.Build.propsso the package ships its///comments and consumers get IntelliSense. Until now no SharpAstro package shipped XML docs.*.Tests) rather thanIsPackable, which test projects set in their own csproj, after the props file is read.<param>when its siblings have one) are silenced: the point is to ship the docs that exist, not to demand them everywhere. Broken crefs and paramrefs still warn.The Release build has no doc warnings.
🤖 Generated with Claude Code
https://claude.ai/code/session_01RPZU4uiM2Z5d4NWmzLqnJv