Bug #4307
closed.NET API Documentation: type hierarchy for XdmNode does not show XdmValue as an ancestor
100%
Description
In the .NET API Documentation, the type hierarchy for XdmNode
is shown as
System.Object
Saxon.Api.XdmItem
Saxon.Api.XdmNode
The fact that XdmItem
is a subclass of XdmValue
is not shown; although on the page for XdmItem
, the hierarchy is shown as Object/XdmValue/XdmItem
.
The same applies to other subclasses of XdmItem, for example XdmAtomicValue.
The same problem affects 9.8 except that the top level System.Object
was not shown in the class hierarchy.
Updated by Debbie Lockett over 4 years ago
- Status changed from New to In Progress
- Applies to branch 9.9, trunk added
Changes committed on 9.9 and 10.0 branches in MyDotNet/doctools/merge.xsl and convert-to-jel-package.xsl, to produce full type hierarchy (rather than just 1 or 2 level hierarchy).
The 9.9 documentation will be updated online with the next maintenance release.
I am not going to fix the issue on the 9.8 branch. Note that Bug #3990 fixed various other issues with the .NET API documentation from 9.9 only.
Also note that the type hierarchy is not included in the HTML version of the .NET API documentation at all. I will look at adding this for 10.0.
Updated by Debbie Lockett over 4 years ago
- Status changed from In Progress to Resolved
- Fix Committed on Branch 9.9, trunk added
Updated by O'Neil Delpratt over 4 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.9.1.5 added
Bug fix applied in the Saxon 9.9.1.5 maintenance release.
Please register to edit this issue