Fix DocFX XML documentation include tags (Issue #11) #72
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.
Summary
This PR fixes the DocFX documentation generation issue described in #11 where XML
<include>
tags were failing to inherit documentation comments from theISynchronization
interface.Changes Made
ReaderWriterLockSynchronization.cs
andUnsynchronization.cs
<inheritdoc/>
tags to properly inherit documentation from theISynchronization
interfaceRoot Cause
The issue was caused by XML
<include>
tags referencing non-existent build artifacts:These tags were pointing to XML files that don't exist in the repository, causing DocFX to fail when trying to process the documentation.
Solution
Since both
ReaderWriterLockSynchronization
andUnsynchronization
classes implement theISynchronization
interface, which already contains comprehensive XML documentation, using<inheritdoc/>
is the proper solution. This allows DocFX to correctly inherit and display the documentation from the interface.Testing
dotnet build -c Release
)dotnet test -c Release
)Fixes #11
🤖 Generated with Claude Code