Fix DocFX indexer comments inheritance by removing problematic include tags #85
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
<include>tags<include>references to external XML files with proper<inheritdoc/>tags<include>tags for documentation inheritance as mentioned in dotnet/docfx#2328Changes Made
Fixed documentation in the following files by removing problematic
<include>tags:Indexer Documentation
Property Documentation
Method Documentation
Solution Approach
The issue was caused by the combination of
/// <inheritdoc/>tags with/// <include file='...'>tags. DocFX handles standard<inheritdoc/>tags properly but fails to process the external XML file references from<include>tags.By removing the
<include>tags and relying solely on<inheritdoc/>, the documentation inheritance now works correctly as the base interfaces (likeIArrayMemory<TElement>) already contain proper XML documentation.Test Results
Resolves #16
🤖 Generated with Claude Code